andresnator Activation Contract
Load this skill when reviewing refactor plans for: single responsibility, SRP, reasons to change.
Hard Rules
- Identify separate business rules, orchestration, IO, mapping, validation, and formatting responsibilities.
- Recommend Extract Class or Move Method only when cohesion improves.
- Avoid splitting code merely because it is long.
- Preserve observable behavior; label functional changes as follow-up.
- Require evidence for every recommendation, or mark it as a hypothesis.
Decision Gates
| 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. |
Execution Steps
- Inspect the target and nearby tests only as needed for this lens.
- Identify findings that match this skill's responsibility.
- Recommend the smallest safe behavior-preserving refactor.
- Add validation and rollback steps for each recommendation.
Output Contract
Return structured findings for the calling reviewer. Return no_findings when this lens has no material issue.
References
None.