adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as…
Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.
$ npx -y skills add sd0xdev/sd0x-dev-flow --skill check-coverage --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/check-coverageContext 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.
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
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: 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
| 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 | ✅/❌ |
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.
Repo: sd0xdev/sd0x-dev-flow
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as…
Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions. Reads…
Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not…
Industry best practices conformance audit with mandatory adversarial debate. Produces audit artifact: verdict (OK/WARN/FAIL) + gap roadmap + debate proof. Use…
Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore).…
Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says…