Agent skill

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.

Stars 33
Forks 4

Install this agent skill to your Project

npx add-skill https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/python3-development/skills/comprehensive-test-review

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:

markdown
## 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.

Expand your agent's capabilities with these related and highly-rated skills.

Jamie-BitFlight/claude_skills

ccc

This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the index', 'ccc', 'cocoindex-code'.

33 4
Explore
Jamie-BitFlight/claude_skills

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

33 4
Explore
Jamie-BitFlight/claude_skills

delegate

Quick delegation template for sub-agent prompts. Use when assigning work to a sub-agent, before invoking the Agent tool, or when preparing prompts for specialized agents. Provides the WHERE-WHAT-WHY framework. For comprehensive delegation guidance, activate the agent-orchestration how-to-delegate skill.

33 4
Explore
Jamie-BitFlight/claude_skills

swarm-spawning

Spawn agents and teammates in Claude Code swarms. Use when choosing between subagents vs teammates, selecting agent types (Explore, Plan, general-purpose, plugin agents), configuring spawn backends (in-process, tmux, iterm2), or setting environment variables for spawned agents.

33 4
Explore
Jamie-BitFlight/claude_skills

knowledge-explorer

Manage the research/ knowledge base (KB) of tool and library research entries. Use when browsing KB topics, adding new research entries, updating existing entries with dated revisions, fetching GitHub repo metadata into a draft KB entry, or migrating old-format entries to skill-spec frontmatter. Triggers on tasks like "what do we have on X", "add this to the KB", "update the KB entry for Y", "fetch github info for owner/repo", or "migrate old entries".

33 4
Explore
Jamie-BitFlight/claude_skills

design-anti-patterns

Enforce anti-AI UI design rules based on the Uncodixfy methodology. Use when generating HTML, CSS, React, Vue, Svelte, or any frontend UI code. Prevents "Codex UI" — the generic AI aesthetic of soft gradients, floating panels, oversized rounded corners, glassmorphism, hero sections in dashboards, and decorative copy. Applies constraints from Linear/Raycast/Stripe/GitHub design philosophy: functional, honest, human-designed interfaces. Triggers on: UI generation, dashboard building, frontend component creation, CSS styling, landing page design, or any task producing visual interface code.

33 4
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results