What problem does it solve?
Refactors become risky and hard to review when they’re too large, bundled with unrelated changes, or undertaken without sufficient test coverage to confirm behavior hasn’t drifted.
Core Features & Use Cases
- Stepwise refactor planning: Break the reorganization into small, individually-verifiable increments that compile and pass tests.
- Blast-radius mapping: Identify every caller affected by symbol moves/renames/contract changes to avoid surprise coupling.
- Test-coverage gating and rollback planning: Start by confirming or adding characterisation tests, identify the riskiest step to execute last, and define rollback strategy per-step or for the overall refactor.
Quick Start
Ask an AI to produce a refactor plan for moving a module and renaming public symbols, including blast radius, test coverage status, sequential mechanical edits, and a rollback strategy.