Refactoring
Improve code structure without changing behavior. One small step at a time.
Iron Law: ONE REFACTORING → TEST → COMMIT. Never batch changes.
When to Use
Answer IN ORDER. Stop at first match:
- User says "refactor", "clean up", "restructure"? → Use this skill
- User asks to "extract", "rename", "simplify"? → Use this skill
- Code smell identified? → Use this skill
- User wants to add feature or fix bug? → Skip (use tdd-enforcer)
- User wants formatting/style fixes? →
[Description truncada. Veja o README completo no GitHub.]