Test Coverage Reviewer
Evaluates test suites for meaningful coverage, ensuring assertions actually verify program behavior.
Install
mkdir -p .claude/skills/test-coverage-reviewer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14616" && unzip -o skill.zip -d .claude/skills/test-coverage-reviewer && rm skill.zipInstalls to .claude/skills/test-coverage-reviewer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Reviews test quality, assertions, and edge case coverageKey capabilities
- →Review each test file completely.
- →Verify that every test has meaningful assertions.
- →Check for missing edge cases or scenarios.
- →Ensure no mocked business logic on the thing being tested.
- →Confirm test names describe expected behavior.
How it works
The skill reads test files and evaluates them against criteria for meaningful assertions, edge case coverage, and proper mocking, then categorizes their quality.
Inputs & outputs
When to use Test Coverage Reviewer
- →Reviewing test files for assertion quality
- →Identifying missing edge case coverage
- →Checking for mocked business logic issues
About this skill
Test Coverage Reviewer
Role
Review tests for meaningful assertions, edge case coverage, and absence of cargo-cult patterns. Ensures tests actually verify behavior, not just run without errors.
Instructions
- Read each test file completely
- Verify every test has meaningful assertions (not just expect(true))
- Check that tests would fail if the implementation is wrong
- Look for missing edge cases (empty input, nulls, boundaries)
- Verify no mocked business logic (vi.mock on the thing being tested)
- Check test names describe expected behavior
- Ensure property-based tests exist for pure functions
- For many test files, spawn opus subagents to review test files in parallel (1 per test file).
Literature
- Consult
docs/compound/research/tdd/for test quality assessment and coverage methodology - Consult
docs/compound/research/property-testing/for property-based testing theory - Run
ca knowledge "test coverage quality"for indexed knowledge
Collaboration
Share cross-cutting findings via SendMessage: cargo-cult tests hiding security issues go to security-reviewer; unnecessary test complexity goes to simplicity-reviewer.
Deployment
AgentTeam member in the review phase. Spawned via TeamCreate. Communicate with teammates via SendMessage.
Output Format
- CARGO-CULT: Test passes regardless of implementation
- GAP: Missing edge case or scenario
- WEAK: Assertion exists but is insufficient
- GOOD: Test is meaningful and complete
When not to use it
- →When only running tests without quality review is needed.
- →When tests are known to be high quality and complete.
- →When the goal is to write new tests rather than review existing ones.
Limitations
- →The skill focuses on test quality, not on fixing implementation code.
- →The skill relies on specific literature for test quality assessment.
- →The skill can spawn subagents for parallel review, which may have resource implications.
How it compares
This workflow specifically reviews the quality and effectiveness of existing tests, identifying common anti-patterns and gaps, unlike simply executing tests or checking code coverage metrics.
Compared to similar skills
Test Coverage Reviewer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| Test Coverage Reviewer (this skill) | 0 | 4mo | No flags | Advanced |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| test-cases | 57 | 7mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
test-cases
cexll
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
reviewing-code
CaptainCrouton89
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
wcag-audit-patterns
wshobson
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
code-coverage-with-gcov
gadievron
Add gcov code coverage instrumentation to C/C++ projects