416 B
416 B
Skill: Safe Refactor
When to Use
- Simplifying existing logic
- Reducing duplication
- Renaming symbols without behavior changes
Steps
- Confirm no behavior change is intended.
- Refactor in small, reversible steps.
- Keep interfaces stable unless instructed.
- Run minimal verification (see mcp/testing.md).
Do Not
- Do not mix refactors with feature changes.
- Do not reformat unrelated code.