test-gap-analyzer

Detect untested functions and uncovered branches in multi-language repositories, generating risk-ranked test specifications.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill test-gap-analyzer-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-gap-analyzer
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/test-gap-analyzer
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill test-gap-analyzer-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates discovery of untested functions, uncovered branches, missing edge cases, and regression debt so teams can prioritize tests by actual bug risk instead of guessing or hoping coverage numbers improve.

Core Features & Use Cases

  • Risk-ranked gap detection: Scans coverage outputs and ranks gaps by a risk score that combines complexity, recent change frequency, and user impact.
  • Actionable test targets: Produces prioritized test specifications (unit, integration, E2E, contract, property-based) for P0/P1 gaps to guide engineers and testers.
  • Self-improvement loop: Measures coverage deltas and flaky-test impact to re-rank gaps and feed the next sprint or quality review.
  • Use case: Run this before a release to identify top regression and branch gaps to include in the release sprint, or run post-incident to close regression debt.

Quick Start

Generate a prioritized test gap report for the repository and output the top ten P0 test targets as actionable test specifications.

Frequently Asked Questions about test-gap-analyzer

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

FAQPage Schema
How do I prioritize test coverage gaps by bug risk instead of just chasing coverage percentages?

Test coverage gaps can be prioritized by bug risk by analyzing coverage outputs to rank untested functions and branches using a score that combines code complexity, recent change frequency, and user impact. This generates risk-ranked targets for sprint planning.

How do I find missing edge cases and regression gaps in a multi-language repository?

Missing edge cases and regression gaps in a multi-language repository are found by scanning coverage outputs from pytest, vitest, or playwright to detect untested functions and uncovered branches, producing actionable test specifications for the highest risk gaps.

Can I generate test specifications from pytest and vitest coverage reports during release readiness?

Yes, pytest and vitest coverage reports can be consumed to generate prioritized test specifications for unit, integration, E2E, contract, and property-based tests to close P0 and P1 regression gaps during release readiness checks.

What is the best way to close regression debt after a post-bug investigation?

The best way to close regression debt after a post-bug investigation is to run a test gap analysis that consumes coverage metrics, ranks missing edge cases by user impact and complexity, and outputs targeted test specifications to fix the debt.

Does test gap analysis work with playwright coverage outputs for sprint planning?

Yes, test gap analysis works with playwright coverage outputs alongside pytest and vitest, consuming the coverage data to identify uncovered branches and feed risk-ranked test targets directly into sprint planning or periodic quality reviews.