Claude-skill-registry comprehensive-test-review

This skill should be used when the user asks to "review test coverage", "audit test quality", "check tests for completeness", or mentions reviewing pytest test suites. Performs thorough test review following standard checklist for test isolation, mock usage, naming, and coverage.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/comprehensive-test-review" ~/.claude/skills/majiayu000-claude-skill-registry-comprehensive-test-review && rm -rf "$T"
manifest: skills/data/comprehensive-test-review/SKILL.md
source content

Comprehensive Test Review

Perform thorough test review for the specified test files or directories.

When to Use

  • Reviewing test coverage before a release
  • Auditing test quality after major refactoring
  • Checking tests for completeness and best practices
  • Identifying gaps in test suites

Test Review Process

Standard Checklist

Coverage Requirements:

  • Minimum 80% line and branch coverage
  • Critical paths have 95%+ coverage
  • All public functions have at least one test
  • Edge cases are explicitly tested

Test Quality:

  • Tests follow AAA (Arrange-Act-Assert) pattern
  • Test names describe behavior, not implementation
  • Each test verifies one logical unit
  • Tests are isolated and independent

Mocking Standards:

  • Uses pytest-mock (MockerFixture), NOT unittest.mock
  • Mocks are scoped appropriately
  • No over-mocking of implementation details
  • External dependencies are properly stubbed

Type Safety:

  • All fixtures have complete type hints
  • Test functions have
    -> None
    return type
  • Using Python 3.11+ syntax (
    str | None
    , not
    Optional[str]
    )

Additional Examination Points

Beyond the standard checklist:

  • Test Isolation: No shared state between tests
  • Mock Appropriateness: Mocking only external dependencies
  • Execution Time: Identifying slow tests for optimization
  • Flaky Patterns: Tests dependent on timing, order, or external state
  • Naming Clarity: Test names that explain intent and expected behavior

Analysis Process

  1. Gather test files in specified path
  2. Run coverage analysis with
    uv run pytest --cov
  3. Check each test against the standard checklist
  4. Identify gaps in coverage and quality
  5. Generate recommendations prioritized by impact

Output Format

Provide findings in this structure:

## Test Review Summary

### Coverage Analysis
- Overall: X%
- Critical modules: Y%
- Gaps identified: [list]

### Quality Issues
**HIGH Priority:**
- [Issue with location and fix]

**MEDIUM Priority:**
- [Issue with recommendation]

**LOW Priority:**
- [Minor improvements]

### Recommendations
1. [Prioritized action items]

Related Skills

  • python3-test-design: Test architecture planning
  • python-pytest-architect: Test implementation

Related Agent

For implementing test improvements, use the

python-pytest-architect
agent.