refactor

To refactor code safely, you need to isolate changes in a worktree, write characterization tests to document existing behavior, and apply small, validated changes with incremental commits to ensure traceability and reversibility.

Characterization tests document the current behavior of a module before you modify it. You need them during refactoring to create a safety net that catches unintended changes when applying patterns like Extract Method or Introduce Value Object.

Start a refactoring workflow by launching your agent with worktree isolation to sandbox changes away from the main branch. Apply small modifications, verify them with tests, commit after each step, and discard the worktree if the refactoring is rejected.

Yes, this guided refactoring approach is designed specifically for modules exhibiting long methods or high coupling. It applies safety checks and incremental validation to address these code smells without disrupting the software's functionality.

The best way to ensure reversibility during code refactoring is to enforce small-step commits after every validated change. This practice provides traceability and allows straightforward recovery procedures if a specific refactoring step fails.

If a refactoring step fails during validation, the workflow enforces specific recovery procedures. You can revert the failed step using the traceable commit history or completely discard the isolated worktree to restore the original state.