Refactoring Safely
Change structure and design in small steps with tests so behavior stays the same and risk is low.
When to Activate
- User asks to "refactor", "clean up", or "improve without changing behavior"
- Extracting functions, renaming, or reorganizing code
- Paying down tech debt in a controlled way
- Preparing code for a feature (e.g. extract interface so new implementation can be added)
Core Principles
- Behavior preserved — Observable behavior (outputs, API, side ef
[Description truncada. Veja o README completo no GitHub.]