Skip to content
Development
Skill

/check-coverage

Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.

From plugin
sd0x-dev-flow
18899 skills16 agents5 hooks
Install
$ npx -y skills add sd0xdev/sd0x-dev-flow --skill check-coverage --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/check-coverage

Context preview

The summary Claude sees to decide when to auto-load this skill.

Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.

SKILL.md

check-coverage.SKILL.md
name: check-coverage
description: "Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations."
allowed-tools: Read, Grep, Glob, Bash(ls:*), Bash(find:*), Bash(wc:*), Agent

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: 1. Read source: Identify public methods, important branches, error handling 2. Read tests: Identify covered cases 3. 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 | ✅/❌ |
Read more
Ships withsd0x-dev-flow

Language: English | 繁體中文 | 简体中文 | 日本語 | 한국어 | Español The harness layer for Claude Code. Let the model choose the path. Keep "done" verifiable. Full control plane on Claude Code. Skills-only distribution for Codex CLI and other compatible agents.

Get the whole plugin

Other skills on sd0x-dev-flow.