fec-refactoring-validation
Installation
SKILL.md
Skill: Refactoring Validation
Purpose
Define the observable contract and the smallest credible evidence needed to prove that structural edits preserved existing frontend behavior.
Procedure
- Record the relevant behavior contract before substantial edits.
- Classify safety-net coverage as A, B, or C.
- Run and record the pre-change baseline.
- Match verification to the current refactoring risk and affected boundary.
- After every structural step, run the narrowest sufficient check immediately.
- If a newly introduced failure appears, revert that step before broader repair.
- At the end, run the broad gates justified by the affected surface.
- Assign PASS, PARTIAL, or NOT PROVEN from evidence, not optimism.
Pure structural work uses GREEN → REFACTOR → GREEN.