test-coverage-retrofit

Coverage-driven test planning analyzes your codebase to discover architectural patterns and integration points, then generates a phased test plan targeting specific files. This systematic approach focuses retrofit efforts on the most impactful test opportunities rather than writing tests blindly.

Yes, you can generate Vitest tests with coverage targets by running the skill in your project root. It applies Haiku-style guidance to write strict type-safe tests and uses early stopping to automatically halt once your specified coverage threshold is achieved.

Coverage-driven test pattern discovery identifies architectural conventions, integration points, and test opportunities by analyzing existing code coverage. You need it when upgrading legacy projects requiring strict coverage upgrades, ensuring new tests align with project standards rather than introducing inconsistent patterns.

Yes, the two-phase test generation approach writes unit tests first, then generates integration tests if needed. This sequential method ensures foundational isolation before expanding scope, automatically stopping early once the target coverage threshold is met.

Preventing flaky tests during retrofitting requires self-cleaning tests that use dynamic test data and automatic cleanup patterns. This skill enforces test isolation by encouraging cleanup conventions that prevent state pollution across parallel test generation runs.

Automated test retrofitting with Haiku-guided generation relies on discovering existing architectural patterns, meaning poorly structured or undocumented codebases may yield less optimal test plans. Additionally, reaching exactly 95% coverage depends on the accuracy of the underlying Vitest coverage tooling integration.