What problem does it solve?
Refactoring tasks maintain external behavior by enforcing regression tests, ensuring code changes do not alter how the software behaves.
Core Features & Use Cases
- Safe refactoring workflow: isolate changes, run baseline tests, and verify equivalence after edits.
- Incremental changes: apply small, verifiable updates (extracts, renames, module reorganizations) with immediate test feedback.
- Regression-driven guarantees: use dedicated worktrees to isolate development from main branches and compare results.
Quick Start
Create a new git worktree branch dedicated to the refactor, so changes are isolated from the main branch.
Run the baseline test suite to establish the current behavior.
Make small, incremental refactor changes and commit after each successful test.
Run the full regression suite again to verify that behavior remains unchanged.
If tests fail, revert the last change and investigate, then retry.
When complete, delete the worktree and merge the changes back to main.