test-coverage-audit

Audit test suites to identify coverage gaps and quality risks.

2|1|Updated Mar 18, 2026

Search Tags:#testing #qa #audit #roadmap #improvements #test-coverage

Ready to run

npx skills add https://github.com/harshitsinghbhandari/domain-expansion --skill test-coverage-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-coverage-audit
Source: https://github.com/harshitsinghbhandari/domain-expansion/tree/main/skills/test-coverage-audit
Command: npx skills add https://github.com/harshitsinghbhandari/domain-expansion --skill test-coverage-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits test suites to identify coverage gaps, brittle assertions, and quality risks.

Core Features & Use Cases

Two-phase evaluation that surfaces coverage gaps and strategy for mitigations.
Generates an audit report and an improvement roadmap to guide testing investments.
Produces artifacts (audit.md and improvements.md) to document findings and actions.

Quick Start

Provide the test and source files you want audited to begin.

Frequently Asked Questions about test-coverage-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit my test suite for coverage gaps and quality risks?▼

To audit a test suite for coverage gaps, you provide your source and test files to generate a ruthless audit report. The evaluation identifies brittle assertions and quality risks, outputting detailed findings to audit.md.

What is the best way to create a test improvement roadmap?▼

The best way to create a test improvement roadmap is by evaluating your existing tests to surface quality risks. This generates an improvements.md file that provides a prioritized path for guiding your testing investments.

Can I audit end-to-end and integration tests with this approach?▼

Yes, you can audit end-to-end and integration tests. The evaluation is applicable across unit, integration, and end-to-end tests within software projects to assess brittle assertions and coverage gaps comprehensively.

Do I need to provide source files to identify brittle assertions?▼

Yes, you need to provide both the test and source files. Supplying both allows the audit to accurately identify brittle assertions and coverage gaps by evaluating the test suite against the actual implementation.

What does a brutal test audit include in the final report?▼

A brutal test audit includes a detailed evaluation of coverage gaps, brittle assertions, and quality risks. It produces two artifacts: audit.md for findings and improvements.md for a prioritized improvement roadmap.