Source profileQuality 91/100

Jamie-BitFlight/claude_skills/plugins/python3-development/skills/comprehensive-test-review/SKILL.md

comprehensive-test-review

Use when reviewing pytest test suites for coverage, isolation, mock usage, naming conventions, or completeness. Activates on requests like "review test coverage", "audit test quality", or "check tests for completeness". Performs thorough checklist-driven review for test isolation, mock correctness, AAA pattern adherence, and naming standards.

Source repository stars
64
Declared platforms
0
Static risk flags
0
Last source update
2026-08-25
Source checked
2026-08-25

Decision brief

What it does: where it fits

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

Best for

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

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/Jamie-BitFlight/claude_skills --skill "plugins/python3-development/skills/comprehensive-test-review"
Safe inspection promptEditorial

Inspect the Agent Skill "comprehensive-test-review" from https://github.com/Jamie-BitFlight/claude_skills/blob/b70ba8737e664d9e2482912e3ddbe7ecb77e0539/plugins/python3-development/skills/comprehensive-test-review/SKILL.md at commit b70ba8737e664d9e2482912e3ddbe7ecb77e0539. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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

    Gather test files in specified pathRun coverage analysis with uv run pytest --covCheck each test against the standard checklist
  2. 02

    Test Review Summary

    HIGH Priority: - [Issue with location and fix]

    Overall: X%Critical modules: Y%Gaps identified: [list]
  3. 03

    When to Use

    Reviewing test coverage before a release

    Reviewing test coverage before a releaseAuditing test quality after major refactoringChecking tests for completeness and best practices
  4. 04

    Testing Standards

    Consult ../python3-development/references/python3-standards.md when auditing against shared testing and quality rules. The checklist below summarizes this skill’s focus; it does not replace the full standards document.

    [ ] Minimum 80% line and branch coverage[ ] Critical paths have 95%+ coverage[ ] All public functions have at least one test

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score91/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars64SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
Jamie-BitFlight/claude_skills
Skill path
plugins/python3-development/skills/comprehensive-test-review/SKILL.md
Commit
b70ba8737e664d9e2482912e3ddbe7ecb77e0539
License
MIT
Collected
2026-08-25
Default branch
main
View the original SKILL.md

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

Testing Standards

Consult ../python3-development/references/python3-standards.md when auditing against shared testing and quality rules. The checklist below summarizes this skill’s focus; it does not replace the full standards document.

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.

Frequently asked questions

What to verify before installation and use

What does the comprehensive-test-review source document cover?

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

How do I install comprehensive-test-review?

The source record exposes this install command: npx skills add https://github.com/Jamie-BitFlight/claude_skills --skill "plugins/python3-development/skills/comprehensive-test-review". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 9164

Jamie-BitFlight/claude_skills

comprehensive-test-review

Performs checklist-driven review of pytest test suites against coverage thresholds (80% line/branch minimum, 95% for critical paths), AAA pattern adherence, pytest-mock usage, test isolation, naming clarity, type hints, and flaky pattern detection. Use when auditing test quality before a release, reviewing coverage gaps, checking tests for completeness or best practices, or validating mocking standards. Accepts a test file or directory as input and outputs prioritized findings grouped by HIGH, M

Computed 975,241

dotnet/skills

test-tagging

Analyzes test suites in any language and tags each test with standardized traits (positive, negative, critical-path, boundary, smoke, regression, integration, performance, security). Use when the user wants to categorize, audit, or label tests with traits. Works across .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest), TS/JS (Jest/Vitest), Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++ — auto-editing when the framework has canonical tag syntax, otherwise report-only. Do not use for writ

Computed 97733

rampstackco/claude-skills

data-warehouse-experimentation

Running experiments out of the data warehouse instead of via dedicated experiment platforms. SQL-based assignment, exposure logging discipline, metric definitions in dbt models, statistical analysis in SQL or Python, variance reduction with CUPED, sequential testing, and the operational tradeoffs vs platforms like Statsig and Optimizely. Triggers on warehouse-native experimentation, run experiments in BigQuery, run experiments in Snowflake, dbt experiments, SQL t-test, CUPED variance reduction,

Computed 97269

Aperivue/medsci-skills

calc-sample-size

Interactive sample size calculator for medical research. Decision-tree guided test selection, reproducible R/Python code, effect size interpretation, and IRB-ready justification text. Supports diagnostic accuracy, agreement, proportions, continuous outcomes, survival, ANOVA, logistic regression, and non-inferiority/equivalence designs.