sd0xdev/check-coverage
skills/check-coverage/SKILL.md
Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.
$ install --global
skillsauthnpx skillsauth add sd0xdev/sd0x-dev-flow check-coverageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 4:01 AM87.4s1 file scanned
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:
- 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 | ✅/❌ |
Related Skills
sd0xdev/zh-tw
documentation
VerifiedTrustedCommunity
Rewrite the previous reply in Traditional Chinese
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/watch-ci
development
VerifiedTrustedCommunity
Monitor GitHub Actions CI runs until completion. Use when: watching CI after push, checking build status, monitoring PR checks, waiting for CI completion, user says 'watch CI', 'check CI', 'CI status', 'monitor build', or /watch-ci. Not for: pushing code (use push-ci), creating PRs (use create-pr). Output: per-run verdict (pass/fail/timeout).
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/verify
development
VerifiedTrustedCommunity
Verification loop — lint -> typecheck -> unit -> integration -> e2e
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/update-docs
development
VerifiedTrustedCommunity
Research current code state then update corresponding docs, ensuring docs stay in sync with code.
147SKILL.mdUpdated Apr 28, 2026