legion-review

Reviews open PRs against issue specs using parallel dimension agents and adversarial finding verification.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/runlegion/legion --skill legion-review-runlegion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legion-review
Source: https://github.com/runlegion/legion/tree/main/plugin/skills/legion-review
Command: npx skills add https://github.com/runlegion/legion --skill legion-review-runlegion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? PR reviews often miss spec mismatches, produce unverified findings, or end with vague approvals that leave real issues untracked. This Skill structures the review stage of a quality pipeline so every finding is adversarially verified and the result is recorded as a HEAD-keyed quality gate that downstream stages can require. ## Core Features & Use Cases - Multi-dimension fan-out: Spawns parallel review agents covering spec-vs-diff, correctness, quality, and security, each focused on a single concern. - Adversarial verification: Every HIGH/MED finding is challenged by a refuter agent that tries to disprove it before it is reported, cutting false positives. - Quality gate recording: Records the decision via legion quality-gate record with a pinned findings schema, so downstream gates can require a clean review on HEAD and findings are tracked toward resolution or disposition. - Use Case: After running legion pr create on a feature branch, invoke this Skill to review the PR against its linked issue's acceptance criteria, get an approved/changes_requested decision with file:line findings, and unblock team sign-off and verification. ## Quick Start Review the open PR for the current branch against its linked issue and record the quality gate result.

Frequently Asked Questions about legion-review

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

FAQPage Schema
How do I review a PR against its issue spec automatically?

Run this Skill after creating the PR with legion pr create. It loads the PR body and linked issue's acceptance criteria, fans out review agents across spec, correctness, quality, and security dimensions, then reports an approved or changes_requested decision with file:line findings.

How does adversarial verification of review findings work?

Every HIGH and MED finding from the dimension agents is sent to a refuter agent prompted to disprove it by reading the cited code. Findings the refuter kills are dropped, and only surviving findings are reported, which reduces false positives.

When should I run legion-review in the quality pipeline?

Run it after legion pr create and the simplify stage, before team sign-off and legion-verify. The gate is keyed on HEAD, so any new commit after the review invalidates it and you must re-run after fixes land.

Why is my quality-gate record with result clean being refused?

A clean result is refused if the same call carries a non-empty findings list, or if prior HIGH/MED findings on the branch are still pending. Record issues first, disposition or ack each finding, then re-record clean with no findings.

Can I use one review agent instead of fanning out to four dimensions?

Yes. For small PRs such as docs-only changes or under roughly 100 changed lines, a single combined agent covering all dimensions is acceptable, and the report should say so. Fan out only when dimensions are genuinely independent work.