code-refactor-executor

To execute a staged code refactoring plan safely, the workspace context is read alongside audit and improvements files to generate an implementation roadmap. Atomic code transformations are then applied behind validation gates to prevent regressions.

Automating code improvements from an audit involves synthesizing the audit recommendations with the current codebase state. A detailed refactor plan is generated with specific stages, targets, and verifications before applying changes.

Gated execution during a codebase refactor works by requiring validations, such as builds or tests, to pass before applying atomic code changes. This ensures phased planning and prevents regressions during the transformation process.

Yes, you can generate a refactoring roadmap automatically. The process scans the target source code, reads the improvement recommendations, and outputs a detailed refactor-plan.md containing stages, targets, actions, and verifications.

To start an automated end-to-end refactor, you need to provide the workspace context and ensure the audit.md and improvements.md files are available. A staged refactor plan ready for execution is then generated from these inputs.

A phased planning approach for source code transformations ensures that changes are applied atomically and gated behind reviews. This prevents regressions by verifying each stage through tests or builds before proceeding.