Activation Contract

Load this skill when reviewing refactor plans for: God Object, Large Class, too many collaborators.

Hard Rules

Look for many unrelated methods, many collaborators, broad state ownership, and mixed domain concepts.
Recommend incremental extraction by cohesive responsibility.
Require characterization tests before risky legacy extractions.
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.