review-swarm

Reviews files with three parallel subagents covering security, test quality, and design correctness.

13|17|Updated Jan 30, 2025
One-click install
npx skills add https://github.com/CodeWithSally/CodeWithSally-Apex-English --skill review-swarm-codewithsally
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-swarm
Source: https://github.com/CodeWithSally/CodeWithSally-Apex-English/tree/main/Sessions/ClaudeCode/Session006/.claude/skills/review-swarm
Command: npx skills add https://github.com/CodeWithSally/CodeWithSally-Apex-English --skill review-swarm-codewithsally

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-pass code reviews tend to under-focus when one reviewer juggles multiple concerns at once, so security holes, hollow tests, and logic bugs slip through. This Skill runs three independent, narrowly-scoped reviewers in parallel and reconciles their verdicts into one actionable call. ## Core Features & Use Cases - Parallel multi-lens review: Launches three read-only subagents simultaneously — security, test-quality, and design-correctness — each blind to the others so findings stay independent. - Structured JSON findings: Every lens returns a verdict (pass/concerns/fail) plus severity-tagged findings with file:line references and one-line recommendations. - Verdict reconciliation: Combines the three verdicts into an overall GO, CAUTION, or STOP call, re-reading the source code itself when lenses disagree rather than defaulting to the loudest finding. - Use Case: Before merging a change to auth.py, run a review swarm to get a security audit, a check that the tests actually assert meaningful behavior, and a logic review — all in the wall-clock time of a single review pass. ## Quick Start Run a review swarm on src/auth.py to get security, test-quality, and design findings with an overall GO, CAUTION, or STOP verdict.

Frequently Asked Questions about review-swarm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a multi-perspective code review on a file?

Invoke /review-swarm with one or more file paths, or ask in plain language to run a review swarm on a target. Three independent subagents review the code in parallel — one for security, one for test quality, one for design correctness — and their findings are merged into a single severity-sorted report.

What does a parallel code review catch that a single review misses?

A reviewer told to hunt for security holes and test weaknesses in the same pass tends to under-focus on both. Three narrow, separately-briefed passes that are blind to each other surface more distinct issues, and parallelism keeps the wall-clock cost at one review instead of three.

Can the review subagents modify my code?

No. All three review subagents are read-only, restricted to Read, Glob, and Grep tools with no Edit, Write, or Bash access. They only report findings with one-line recommendations; applying fixes is a separate step.

What happens when the three reviewers disagree on a verdict?

Disagreement triggers a manual re-read of the cited source lines before ruling. If the finding is confirmed, the verdict reflects it; if ruled out, it is downgraded with an explicit explanation; if genuinely ambiguous, the more severe verdict wins by default.

What happens if a reviewer returns malformed output?

A subagent response that does not parse as the expected JSON shape is treated as its own finding and counted as a fail for reconciliation. A malformed response is never silently dropped or interpreted as a clean bill of health.