review-tests

Comprehensive test review using parallel test-reviewer agents.

24 stars

Best use case

review-tests is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Comprehensive test review using parallel test-reviewer agents.

Teams using review-tests should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/review-tests/SKILL.md --create-dirs "https://raw.githubusercontent.com/leogodin217/leos_claude_starter/main/.claude/skills/review-tests/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/review-tests/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How review-tests Compares

Feature / Agentreview-testsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Comprehensive test review using parallel test-reviewer agents.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Review Tests

Orchestrate a comprehensive test review using parallel test-reviewer agents.

## Process

### 1. Discover

Find all test files:
```
Glob: **/test_*.py, **/*_test.py
```

Map each test file to its source:
- `tests/test_foo.py` → `src/.../foo.py`
- `src/.../tests/test_bar.py` → `src/.../bar.py`

Report: "Found N test files covering M source modules"

### 2. Plan Parallelization

Group tests for parallel review. Options:
- By file (maximum parallelism)
- By module (balanced)
- By package (fewer agents)

Default: By module (all tests for a source module → one agent)

### 3. Launch Agents

For each group, launch test-reviewer agent:
```
Task(
    subagent_type="test-reviewer",
    prompt="Review tests.\n\ntest_path: {paths}\nsource_path: {paths}",
    run_in_background=true
)
```

Launch ALL agents in a single message for true parallelism.

### 4. Collect Results

Wait for all agents to complete. Gather structured output.

### 5. Aggregate

Combine findings across all agents:

```markdown
# Test Review Summary

## Overall
- Files reviewed: N
- Tests reviewed: N
- Remove: N | Improve: N | Add: N | Keep: N

## By Priority

### High (Remove - tests with no value)
[List across all files]

### Medium (Add - important gaps)
[List across all files]

### Low (Improve - existing tests to refine)
[List across all files]

## By Module
[Findings grouped by source module]
```

### 6. Recommendations

Based on findings, recommend:
1. Tests to delete immediately
2. Critical gaps to fill
3. Improvements to make
4. Whether overall test health is good/fair/poor

Related Skills

review-sprint

24
from leogodin217/leos_claude_starter

Post-implementation mechanical audit of sprint deliverables.

arch-review

24
from leogodin217/leos_claude_starter

Review architecture documents against code implementation and principles.

verify-sprint

24
from leogodin217/leos_claude_starter

Spec-fidelity verification tracing requirements through code.

session

24
from leogodin217/leos_claude_starter

Analyze Claude Code session transcripts — search, summarize, list, or inspect how a session went.

role-educator

24
from leogodin217/leos_claude_starter

Course designer mode for creating exercises, configs, and QA criteria.

role-architect

24
from leogodin217/leos_claude_starter

System architect mode for designing interfaces, contracts, and architecture decisions.

issue

24
from leogodin217/leos_claude_starter

Create, list, and resolve review issues. Critical issues get individual files for research; warnings and gaps go to a quick-fix checklist.

implement-sprint

24
from leogodin217/leos_claude_starter

Automated sprint implementation with context discipline and quality gates.

get-started

24
from leogodin217/leos_claude_starter

Interactive setup guide for configuring CLAUDE.md and CAPABILITIES.md.

eval-sprint

24
from leogodin217/leos_claude_starter

Adversarial evaluation of sprint spec before implementation.

create-sprint

24
from leogodin217/leos_claude_starter

Guide sprint planning from scope assessment to spec artifacts.

audit-docs

24
from leogodin217/leos_claude_starter

Orchestrate sequential documentation audits with checkpointing and resumption.