super-review:run

Orchestrate multi-agent GitHub PR reviews with evidence-quoted, diff-scoped findings.

Updated May 15, 2026
One-click install
npx skills add https://github.com/mattnowdev/super-review --skill super-review-run
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: super-review:run
Source: https://github.com/mattnowdev/super-review/tree/main/skills/run
Command: npx skills add https://github.com/mattnowdev/super-review --skill super-review-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of noisy, hallucinated, and out-of-scope AI PR reviews by producing a bounded set of actionable findings that are strictly tied to the PR diff and backed by quoted code evidence.

Core Features & Use Cases

  • Evidence-quoted multi-agent review pipeline: runs parallel specialist reviewers, then enforces an evidence-confirmation gate before anything ships.
  • False-positive and verification discipline: re-checks quoted findings against the actual code, then applies cross-reviewer collision checks and an Opus meta-verification pass.
  • Diff-scoped, bounded reporting: keeps output strictly within the PR’s changed lines and caps the number of issues to reduce noise and reviewer overwhelm.
  • Stack-aware sub-skill loading: auto-loads framework/security sub-skill catalogs based on detected technologies (for example React/Next.js/ORM/crypto/web headers/LLM security).

Quick Start

Run super-review in your Claude Code workflow by telling the assistant to review your pull request using the command "/super-review:run" or by pasting the GitHub PR URL and asking for a review.

Frequently Asked Questions about super-review:run

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

FAQPage Schema
How do I get a pull request review that only reports issues actually found in the diff?▼

A diff-scoped PR review uses multi-agent specialist dispatch to analyze only the PR diff, then applies an evidence-quoting false-positive gate to confirm each finding with byte-quote verification before including it in a bounded report.

What is the best way to reduce false positives in AI code reviews?▼

The best way to reduce false positives in AI code reviews is to apply an evidence-confirmation gate that re-checks quoted findings against the actual code, followed by cross-reviewer collision checks and a meta-verification pass to ensure every issue is twice-confirmed.

Can I use Claude Code to review GitHub pull requests for security and correctness?▼

Yes, you can use Claude Code to review GitHub pull requests by orchestrating parallel specialist dispatch across correctness, security, design, migration, performance, frontend, observability, and testing domains, outputting a capped actionable report.

How do multi-agent PR review pipelines handle framework-specific security checks?▼

Multi-agent PR review pipelines handle framework-specific security checks through stack-aware sub-skill loading that auto-detects technologies like React, Next.js, ORM, or crypto libraries and loads corresponding framework and security catalogs for targeted analysis.

Does automated PR review work with diff-from-main detection or do I need an explicit PR number?▼

Automated PR review works with both explicit GitHub PR URLs or numbers and automatic diff-from-main detection, ensuring the multi-phase review pipeline always targets the correct set of changed lines for bounded reporting.

Why does my AI pull request review report issues outside the changed code?▼

AI pull request reviews report issues outside the changed code because they lack a diff-scoped boundary and collision check. Applying a bounded reporting approach with an Opus meta-verification phase keeps findings strictly within the PR diff.