coverage-gap-detection

Identify untested paths and missing coverage in a codebase.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lgerard314/global-plugin --skill coverage-gap-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-gap-detection
Source: https://github.com/lgerard314/global-plugin/tree/main/plugin/skills/coverage-gap-detection
Command: npx skills add https://github.com/lgerard314/global-plugin --skill coverage-gap-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually identifying testing gaps is time-consuming and error-prone. This Skill surfaces untested paths, missing edge-case coverage, and weak test strategies before merging code.

Core Features & Use Cases

  • Automated gap detection across the codebase that surfaces critical untested paths.
  • Edge-case and negative-test identification to strengthen guardrails and reduce regression risk.
  • Prioritized reporting with actionable items that map to integration and boundary tests.

Quick Start

Scan the repository to surface testing gaps and generate a prioritized report.

Frequently Asked Questions about coverage-gap-detection

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

FAQPage Schema
How do I find untested paths and missing test coverage before a merge?

Missing test coverage is identified by evaluating critical paths, error branches, and boundary inputs against a defined test-strategy rubric, surfacing gaps in negative tests and authorization data paths.

What is the best way to identify edge cases and negative tests in my codebase?

Edge-case and negative-test identification works by evaluating error branches and boundary inputs against a defined test-strategy rubric, generating a structured set of findings to strengthen guardrails.

How does gap analysis improve integration test strategy and release confidence?

Gap analysis improves integration test strategy by surfacing untested paths and prioritizing actionable items that map directly to boundary tests, thereby reducing regression risk and increasing release confidence.

Can I scan a completed feature for missing authorization and data-path coverage?

Applied to features just completed or before merge, this evaluates critical paths, error branches, and boundary inputs against a defined test-strategy rubric to surface authorization and data-path coverage gaps.

Does automated gap detection work without configuring external testing dependencies?

Automated gap detection works without external dependencies, scanning the repository directly to surface testing gaps and generate a prioritized report mapping to integration tests.