test-coverage-audit

This skill systematically identifies untested code, stub-only tests, and high-risk modules lacking coverage by analyzing build manifests and test runner outputs to generate a risk-assessed testing roadmap.

The best way is generating a prioritized implementation plan that balances unit, functional, and integration tests, targeting high-risk modules first to maximize confidence without wasting effort on low-value tests.

You generate a prioritized testing roadmap by parsing CI configurations and test runner outputs to analyze current coverage, which produces a risk-assessed plan targeting untested code and stub-only tests.

Yes, this test coverage audit works for untested software projects by providing a structured, risk-based approach to systematically identify coverage gaps and plan necessary test implementation across unit, functional, and integration suites.

You should use a risk-based approach to improve test coverage because it prevents wasting time on low-value tests by generating a ranked plan that focuses implementation efforts directly on high-risk modules lacking coverage.