Skill

check-coverage

Assesses unit, integration, and E2E test coverage for features from docs, identifies gaps in source files by severity (critical to nice-to-have), and recommends new tests with structured report.

testing

npx claudepluginhub sd0xdev/sd0x-dev-flow --plugin sd0x-dev-flow

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash(ls:*)Bash(find:*)Bash(wc:*)Agent

Preview

- Keywords: check coverage, test coverage, coverage analysis, coverage gaps, check-coverage

SKILL.md

Similar Skills

test-coverage

104

Analyzes test coverage reports (lcov, cobertura, istanbul) to identify gaps in lines/branches/functions, map to requirements, recommend tests, and track trends.

sdlc

test-review

147

Reviews test coverage and sufficiency via Codex MCP, identifies gaps, audits quality across 5 dimensions. Supports git diff auto-detection, file targeting, and AC traceability from request docs.

3 files7 tools

sd0x-dev-flow

coverage

Analyzes code-level test coverage for lines, branches, functions, and statements using npm test tools, identifies gaps, prioritizes by risk, and recommends specific tests to add. Useful post-test run for JS projects.

1 file4 tools

universal-dev-standards

Stats

Stars147

Forks20

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Test Coverage Analysis

Trigger

Keywords: check coverage, test coverage, coverage analysis, coverage gaps, check-coverage

When NOT to Use

Test sufficiency review via Codex (use /codex-test-review)
Generating tests (use /codex-test-gen)
Running tests (use /verify)

Parent Skill Reference

See @skills/test-review/SKILL.md for Codex-based test review workflow.

Agent Dispatch

Agent({
  description: "Assess three-layer test coverage and identify gaps",
  subagent_type: "coverage-analyst",
  prompt: `Assess Unit / Integration / E2E test coverage for the feature docs at: $ARGUMENTS
Follow the steps defined in this skill.`
})

Task

Step 1: Read Feature Documentation

Read specified feature docs. Extract:

Feature name and objectives
Involved Service / Provider / Entity
Core flows and boundary conditions

Step 2: Identify Related Source Code

Search related source code based on feature documentation. Build source code inventory.

Step 3: Map Test Files

Check whether each source file has corresponding tests (unit, integration, e2e).

Step 4: Analyze Coverage Gaps

For each source file:

Read source: Identify public methods, important branches, error handling
Read tests: Identify covered cases
Compare gaps: missing methods, uncovered branches, untested error scenarios

Step 5: Classify and Recommend

Severity	Description
🔴 Critical	Core logic, data writes, amount calculations
🟠 Major	Important branches, error handling
🟡 Minor	Edge cases, utility functions
⚪ Nice-to-have	Logging, formatting

Output

# Test Coverage Analysis Report

## Feature Overview
- Feature name: <from documentation>
- Documentation path: $ARGUMENTS
- Related modules: <list>

## Current Coverage
| Module | Source Path | Test Path | Coverage Status |
|--------|------------|-----------|----------------|

## Coverage Gaps
### 🔴 Critical
### 🟠 Major
### 🟡 Minor

## Recommended New Tests
| Priority | Test Type | Test Case | Target File |
|----------|-----------|-----------|-------------|

## Coverage Summary
| Metric | Status |
|--------|--------|
| Feature coverage | X/Y (Z%) |
| Happy path | ✅/❌ |
| Error path | ✅/❌ |
| Edge cases | ✅/❌ |