Claude skill
Test Health
Test Health is a Claude skill in the Sd0x Harness plugin. Holistic test coverage measurement. Use when: assessing test health, measuring coverage trends, quantitative + qualitative test audit.
What it does
The description in the skill's SKILL.md, which Claude reads to decide when to use it:
Holistic test coverage measurement. Use when: assessing test health, measuring coverage trends, quantitative + qualitative test audit. Not for: running tests (use verify), reviewing test sufficiency only (use codex-test-review), generating tests (use codex-test-gen). Output: multi-dimensional dashboard with coverage metrics + test inventory + trend.
The skill's instructions (about 1,490 words) cover:
- Trigger
- When NOT to Use
- Workflow
- Modes
- Quick Mode Workflow
- Full Mode Workflow
- Phase A: Feature Coverage
- Phase B: Test Inventory + Coverage Collection
- Phase C: Qualitative Review
- Phase D: Aggregate + Trend
- Coverage Collection Strategy (Consume-First)
- Output: Quick Dashboard
How to use it
- Test Health comes inside the Sd0x Harness plugin, so you get it by installing that plugin, along with its 101 other skills. A plugin installs as one unit, with all its skills. The plugin's page has the install steps, and plugins are saved to your Claude account.
- Ask Claude for the task. When your request matches the skill's description, Claude loads it.
- To pick it yourself in Claude chat, type
/or click + and choose test-health. In Claude Code and Cowork, type:/sd0x-dev-flow:test-health
Source
- Plugin
- Sd0x Harness
- SKILL.md
- View on GitHub
- Repo stars
- 196
- Repo last pushed
- Nov 16, 2026
- Checked
- Nov 16, 2026
More skills in Sd0x Harness
- Test ReviewTest coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit.
- UI First PrinciplesFirst-principles UI/IA reasoning: turns a `<scenario>` + API field set into JTBD analysis, principle-anchored field-priority decisions, anti-pattern findings, and a bidirectional UI↔API gap report.
- Update DocsResearch current code state then update corresponding docs, ensuring docs stay in sync with code.
- VerifyVerification loop — lint -> typecheck -> unit -> integration -> e2e
- Watch CiMonitor GitHub Actions CI runs until completion.
- Zh TwRewrite the previous reply in Traditional Chinese
- AdrWrite an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature>/adr-<NNN>-<title>.md with a 3-digit…
- Agentctl SetupInstall and set up the optional agentctl mod (task scope, refusal before execution, evidence that goes stale, model-free hand-over) — checks the environment, installs after approval, builds the…
- ArchitectureArchitecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions.
- AskContext-aware Q&A with auto context gathering.
- Best PracticesIndustry best practices conformance audit with mandatory adversarial debate.
- Bug FixBug fix workflow. Use when: fixing bugs, resolving issues, regression fixes.
- Bump VersionBump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version.
- Check CoverageComprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.
- Claude HealthClaude Code config health check + plugin sync.
- Code ExplorePure Claude code investigation. Use when: tracing execution paths, understanding architecture, diagnosing issues.
- Code InvestigateDual-perspective code investigation. Use when: deep code analysis needing both Claude and Codex perspectives.
- Codex ArchitectCodex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design.
- Codex BrainstormAdversarial brainstorming via Claude+Codex debate.
- Codex CLI ReviewCode review via Codex CLI with full disk access.
- Codex Code ReviewCode review using Codex exec. Use when: PR review, code audit, second opinion on changes.
- Codex ExplainExplain complex code via Codex exec. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code.
- Codex ImplementImplement features via Codex exec. Use when: writing new code from specs, implementing features, Codex-driven development.
- Codex ReviewFull second-opinion using Codex exec (with lint:fix + build). Supports review loop with context preservation.