swarm-pr-review

Orchestrates multi-agent pull request review with parallel explorer lanes, independent validation, and critic challenge.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill swarm-pr-review-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swarm-pr-review
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/swarm-pr-review
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill swarm-pr-review-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deep pull request reviews often miss critical bugs or drown reviewers in unvalidated false positives. This Skill structures PR review as a multi-phase pipeline that maximizes recall through parallel exploration while enforcing independent validation before any finding is reported. ## Core Features & Use Cases - Parallel Explorer Lanes: Six base lanes (correctness, security, dependencies, docs/intent, tests, performance) plus triggered micro-lanes for risk areas like git safety, schema drift, and config ratchets. - Independent Validation Pipeline: Reviewer subagents confirm, disprove, or classify every candidate with file:line evidence, followed by critic challenge for HIGH/CRITICAL findings. - Obligation Extraction & Metrics: Reconstructs what the PR must deliver from checkboxes, issues, and commits, then records review quality metrics and knowledge writeback. - Use Case: When reviewing a large feature branch touching authentication and schema code, run this workflow to get grouped, evidence-backed findings with a merge recommendation (APPROVE, REQUEST_CHANGES, or BLOCK) instead of ad-hoc comments. ## Quick Start Ask the AI to run a swarm PR review on the current branch diff against main and report validated findings with a merge recommendation.

Frequently Asked Questions about swarm-pr-review

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

FAQPage Schema
How do I run a multi-agent code review on a pull request?▼

Invoke the swarm-pr-review workflow with a PR URL, branch, or commit range. It checks out the target branch, builds a context pack, launches parallel explorer lanes, and routes candidates through independent reviewer validation before reporting findings.

How does this review workflow reduce false positives?▼

Explorers only produce candidates; they cannot confirm findings. Independent reviewer subagents re-read file:line evidence and classify each candidate as CONFIRMED, DISPROVED, UNVERIFIED, or PRE_EXISTING, and a critic challenges all HIGH and CRITICAL findings before reporting.

What is council mode in PR review?▼

Council mode is an opt-in adversarial variant triggered by explicit phrases like 'council' or 'assume all work is wrong'. Agents return only EVIDENCE_FOUND, SUSPICIOUS, or CLEAN states, and an independent reviewer still classifies every candidate before synthesis.

Can the orchestrator validate findings itself during review?▼

No. The Anti-Self-Review Rule forbids the orchestrator from confirming or disproving explorer candidates in the default workflow. It may only scope, route, and synthesize; validation must be delegated to reviewer subagents.

When should I not use this deep review workflow?▼

Avoid it for trivial changes like typo fixes or single-line config edits where full multi-lane exploration costs more than the risk justifies. It is designed for PRs touching security, state, schema, permissions, or cross-file contracts.