Activation Contract

Load this skill when reviewing refactor plans for: logging, observability, metrics, traces.

Hard Rules

Flag noisy, duplicated, wrong-level, context-free, sensitive, or repeated exception logs.
Recommend logs only at useful boundaries, decisions, and failure points.
Use observability to validate before/after behavior without changing business behavior.
Preserve observable behavior; label functional changes as follow-up.
Require evidence for every recommendation, or mark it as a hypothesis.

Signal	Action
Concrete evidence exists	Create a finding with file, lines, symbol, benefit, validation, and rollback.
Evidence is incomplete	Mark as hypothesis and lower confidence.
Recommendation is cosmetic or speculative	Omit it unless maintainability benefit is clear.