refactoring-expert

To safely refactor code without altering external behavior, apply incremental, phase-driven steps that enforce analysis, planning, and controlled application. This process minimizes risk by verifying small, testable changes before integration.

The best way to refactor a large codebase iteratively is using a phase-driven workflow that guides you through parse inputs, analysis, and staged changes. This ensures traceable, low-risk refactors across modules.

Incremental refactoring maintains code quality by breaking down structural improvements into small, verifiable steps. This enforces safe changes, produces before/after diffs, and generates change summaries for audits.

Yes, you can apply single responsibility principle refactors across multiple modules safely by following a phase-driven workflow. It enforces defined checks and documentation requirements for low-risk structural changes.

You should not use incremental refactoring when a complete system rewrite is required rather than structural improvement, as this approach focuses specifically on safe changes that preserve existing external behavior.