refactor-verify

To verify a code refactor and prevent regressions, capture a baseline of tests, metrics, and git state before changing code, then run post-change verification to compare results and generate a diff report.

Baseline capture in refactoring records your tests, code metrics, and git state before changes. It is needed to establish a reference point for post-change verification to detect regressions and track code quality differences.

You integrate refactor verification into a CI pipeline by running the baseline capture step before changes and the verification step after. This guards refactors in automated workflows by comparing metrics and test results.

Yes, you need pnpm and git installed to verify refactors locally. These dependencies are required to record the git state, manage packages, and execute the scripts that capture baseline metrics.

The best way to compare code metrics before and after a refactor is using an automated verification tool that records a baseline, re-measures metrics post-change, and generates a diff report with a final verdict.

Yes, you can use this refactor verification for local development workflows. It applies to both local IDE environments and CI pipelines to safely compare pre- and post-refactor results across tests and metrics.