find-coverage-gaps

Identify code files with missing test coverage and rank them by risk.

5|Updated Jul 25, 2025

Search Tags:#testing #coverage #code-coverage #quality-assurance #risk-analysis #test-strategy

Ready to run

npx skills add https://github.com/tomzx/agents --skill find-coverage-gaps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: find-coverage-gaps
Source: https://github.com/tomzx/agents/tree/main/skills/find-coverage-gaps
Command: npx skills add https://github.com/tomzx/agents --skill find-coverage-gaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams locate files and modules with missing or insufficient test coverage and prioritizes them by risk to guide where to invest testing effort.

Core Features & Use Cases

Automatic gap discovery: scans the repository to surface uncovered or under-tested files and modules.
Risk-based prioritization: ranks gaps by a calculated risk score using coverage, churn, and code complexity.
Actionable recommendations: generates guidance on tests to write, including unit and integration scenarios.

Quick Start

Run this skill at the repository root to generate a prioritized gaps report.

Frequently Asked Questions about find-coverage-gaps

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

FAQPage Schema

How do I identify test coverage gaps in my codebase?▼

To identify test coverage gaps, you need to run your project's test suite with coverage data enabled. This Skill parses standard coverage reports to scan the repository and surface uncovered or under-tested files and modules automatically.

What is the best way to prioritize which code files need tests?▼

The best way to prioritize missing tests is by calculating a risk score based on code coverage, file churn, and complexity. This approach ranks test-coverage gaps so you can direct testing effort toward the highest-risk areas first.

How do I analyze risk for untested code across multiple languages?▼

You can analyze risk for untested code across multiple languages by applying a risk calculation engine repository-wide. It computes scores from standard coverage reports, supporting diverse test ecosystems to generate a prioritized gaps list.

Do I need to run the test suite before analyzing test-coverage gaps?▼

Yes, you must run the test suite with coverage data before analysis. The Skill requires standard coverage reports generated from your test execution to calculate risk scores and identify files with missing or insufficient test coverage.

Can I get actionable recommendations for unit and integration tests to write?▼

Yes, the Skill generates actionable recommendations for tests to write. After identifying test-coverage gaps and ranking them by risk, it provides specific guidance on both unit and integration testing scenarios to improve coverage.

What factors are used to rank missing test coverage by risk?▼

Missing test coverage is ranked by risk using three factors: code coverage percentage, file churn, and code complexity. This combined risk score helps prioritize test investments toward areas with the highest potential for defects.