Best for
- Reviewing test coverage before a release
- Auditing test quality after major refactoring
- Checking tests for completeness and best practices
Jamie-BitFlight/claude_skills/plugins/python3-development/skills/comprehensive-test-review/SKILL.md
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.
Decision brief
Perform thorough test review for the specified test files or directories.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/Jamie-BitFlight/claude_skills --skill "plugins/python3-development/skills/comprehensive-test-review"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
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
HIGH Priority: - [Issue with location and fix]
Reviewing test coverage before a release
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.
Permission review
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
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 91/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 64 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Perform thorough test review for the specified test files or directories.
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:
Test Quality:
Mocking Standards:
Type Safety:
-> None return typestr | None, not Optional[str])Beyond the standard checklist:
uv run pytest --covProvide 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]
For implementing test improvements, use the python-pytest-architect agent.
Frequently asked questions
Perform thorough test review for the specified test files or directories.
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
Jamie-BitFlight/claude_skills
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
dotnet/skills
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
rampstackco/claude-skills
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,
Aperivue/medsci-skills
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.