refactorpass

Automated code cleanup applies a structured, behavior-preserving matrix to your pull request branch. It removes dead code, aligns conventions, and collapses awkward control flow while ensuring non-breaking modifications before review.

Behavior-preserving refactoring systematically improves code quality without changing its functional output. You need it when a pull request accumulates technical debt, ensuring reviewers focus on logic rather than style or messy control flow.

Yes, automated refactoring requires integration with your local Git environment. It performs pre-flight context checks to verify branch state and sufficient context window headroom before safely applying any cleanup modifications.

The best way to remove dead code before a review is executing a three-lane cleanup matrix covering simplicity, correctness-preserving improvements, and API alignment. This ensures systematic, non-breaking technical debt removal.

Automated PR cleanup is explicitly behavior-preserving, meaning it applies non-breaking modifications to align conventions and remove dead code without altering the functional output or logic of your recent changes.

Automated code refactoring passes require sufficient context window headroom and a verified branch state to function properly. The process is strictly limited to pre-defined cleanup matrices, meaning it cannot handle complex, logic-altering refactoring.