cc-refactoring-guidance

Safe refactoring requires a structured plan that documents required steps, prerequisites, and verification criteria to ensure behavior preservation. You identify target modules, sequence small incremental changes, and run tests after each step to reduce regression risk.

Refactoring decision guidance compares refactor, rewrite, and fix-first approaches when behavior must be preserved. You evaluate the risk and traceability of each option to determine the safest path for improving code structure across multiple modules.

Risk assessment for codebase modification involves documenting steps, prerequisites, and verification results to reduce regression risk. You apply rules, checklists, and gates to ensure changes remain small, verifiable, and reversible throughout the refactoring process.

Version control enables reversible refactoring by saving state before you identify target modules and apply changes. You commit small incremental steps, run tests after each modification, and document verification criteria to ensure behavior preservation.

Yes, the refactoring protocol applies to codebases undergoing modification, improvement, or decisions between refactor and rewrite. You identify safe opportunities, produce a structured plan, and document verification criteria to preserve behavior across modules.

Incremental refactoring requires existing tests and version control to verify behavior preservation. Without these prerequisites, changes may introduce regressions, making the protocol less effective for large codebases lacking verification criteria and traceability.