From sd0x-dev-flow
Assesses three-layer test coverage (unit/integration/E2E) by mapping source code to tests, identifying gaps, and recommending new tests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sd0x-dev-flow:check-coverageThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Keywords: check coverage, test coverage, coverage analysis, coverage gaps, check-coverage
/codex-test-review)/codex-test-gen)/verify)See @skills/test-review/SKILL.md for Codex-based test review workflow.
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.`
})
Read specified feature docs. Extract:
Search related source code based on feature documentation. Build source code inventory.
Check whether each source file has corresponding tests (unit, integration, e2e).
For each source file:
| Severity | Description |
|---|---|
| 🔴 Critical | Core logic, data writes, amount calculations |
| 🟠 Major | Important branches, error handling |
| 🟡 Minor | Edge cases, utility functions |
| ⚪ Nice-to-have | Logging, formatting |
# 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 | ✅/❌ |
npx claudepluginhub sd0xdev/sd0x-dev-flow --plugin sd0x-dev-flowAnalyzes test coverage reports (lcov, cobertura, istanbul) to identify gaps in lines/branches/functions, map to requirements, recommend tests, and track trends.
Reviews test sufficiency and identifies coverage gaps using Codex MCP. Supports file, directory, description, or git-diff input. Includes AC traceability mode for mapping acceptance criteria to test evidence.
Surveys test suites across five phases: unit, integration, E2E (browser), fuzz coverage gaps, and test quality. Produces findings and proposes tickets for remediation.