skills.rest
sQVe
sQVeCOMMUNITY
Explore all skills by this author →
GitHub

find-test-gaps

Map source files to test coverage and identify untested behaviors with concrete bug risks.

Updated Mar 6, 2026
Search Tags:#scope#find#code-analysis#gaps#untested#test-gaps#bug-risk
One-click install
npx skills add https://github.com/sQVe/cape --skill find-test-gaps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-test-gaps
Source: https://github.com/sQVe/cape/tree/main/skills/find-test-gaps
Command: npx skills add https://github.com/sQVe/cape --skill find-test-gaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan a user-specified scope for source code that lacks meaningful test coverage. Map source files to test files, read public APIs, and identify behaviors that ship untested. Output a br epic with one task per module that needs tests.

Core Features & Use Cases

  • Identify gaps in test coverage for a given module, feature, or directory.
  • Map source files to existing tests and surface concrete bug risks for untested paths.
  • Generate a br epic with per-module tasks, each detailing the bug that the missing test would catch.

Quick Start

Provide a structured gap analysis for the specified scope, listing bugs each gap could catch and requested approvals.

Frequently Asked Questions about find-test-gaps

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

FAQPage Schema
How do I find untested code gaps and identify bug risks in my source files?▼

To find untested code gaps, map source files to test coverage and read public APIs to surface untested behaviors. This identifies concrete bug risks tied to missing tests rather than generic coverage notes.

What is the best way to analyze test coverage gaps for a specific module or directory?▼

Analyzing test coverage gaps involves scanning a specified directory or module to map source files against existing tests. It outputs per-module tasks detailing specific bugs that missing tests would catch.

Does this test gap analysis tool require a specific scope or directory to run?▼

Test gap analysis requires a defined scope to function. You must point it to a directory, module, or feature area so it can assess test health and identify untested behaviors within that boundary.

Can I skip trivial files when scanning for untested behaviors in my codebase?▼

Self-checks automatically skip trivial files during the scan for untested behaviors. This ensures the output focuses on per-module gaps with concrete bug risks instead of flagging non-critical source files.

How do I generate actionable tasks for source code that lacks meaningful test coverage?▼

Generate actionable tasks by mapping source files to test files and reading public APIs to identify untested paths. The output is a backlog epic with one task per module detailing the bug to catch.

Why does my test coverage report show no tests instead of concrete bug risks for missing paths?▼

Generic no tests notes lack actionable detail. This analysis maps source files to tests and surfaces concrete bug risks for untested paths, presenting per-module gaps tied to specific failure scenarios.

Related Skills

Explore More Software Engineering Skills→
lis186lis186
46

codebase-overview

Analyze codebase structure to identify project type, architecture patterns, and tech stack.

Community
Basic
seankao31seankao31

mutation-testing

Apply mutation testing to evaluate test suite quality and reveal defects.

Community
Advanced
ResgridResgrid
224

code-review-workflow

Generate severity-ranked code review feedback for .NET changes using Roslyn MCP analysis.

Official
Advanced
bradtaylorsfbradtaylorsf
8

jest-coverage

Configure, execute, and analyze Jest code coverage reports.

Community
Intermediate