Activation Contract

Load this skill when reviewing refactor plans for: small functions, long method, extract method.

Hard Rules

Flag methods with multiple abstraction levels, nested branches, or distinct phases.
Prefer Extract Method when a block has a meaningful domain name.
Prefer Split Phase when parsing/validation/calculation/persistence are interleaved.
Keep recommendations behavior-preserving and incremental.
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.