tdd-refactor-guard

Ensure test coverage before AI-assisted refactoring by verifying the public API surface and validating existing tests. The guard assesses coverage quality and provides a decision framework to proceed, generate missing tests, or stop changes entirely.

Characterization tests capture the current behavior of code before changes are made. You need them for a code refactor when existing test coverage is insufficient, ensuring safety by automatically generating regression tests for the untested public API surface.

Safely clean up code across multiple files and modules by assessing public API surface coverage and validating existing tests first. The guard identifies missing regression tests across modules and proposes characterization tests to capture current behavior before changes.

The best way to guard against regressions during AI-assisted code cleanup is to validate existing tests and assess the public API surface beforehand. The guard provides a clear decision framework: proceed with the refactor, generate missing characterization tests, or stop.

Yes, you can refactor code even if existing tests do not cover the public API surface. The guard detects insufficient coverage and automatically proposes or creates characterization tests to capture current behavior, ensuring the refactor is protected by regression tests.

Your AI-assisted refactor needs a decision framework for test coverage to prevent breaking existing behavior. The guard evaluates the public API surface and returns a proceed, needs tests, or stop decision, ensuring refactors only happen when regression safety is verified.