Learn-skills.dev review-all

Pre-PR review pipeline — runs security, API audit, and scope check agents in parallel. Read-only, no changes. Use before creating PRs or after completing a phase of work.

install

source · Clone the upstream repo

git clone https://github.com/NeverSight/learn-skills.dev

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/NeverSight/learn-skills.dev "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills-md/acedergren/agentic-tools/review-all" ~/.claude/skills/neversight-learn-skills-dev-review-all && rm -rf "$T"

manifest: data/skills-md/acedergren/agentic-tools/review-all/SKILL.md

source content

Review All

Comprehensive pre-PR review that runs specialized reviewers in parallel and synthesizes findings into a single report. Read-only — no changes.

When to Use

Before creating a PR
After completing a phase of work
When you want a full-spectrum code quality check beyond what linting covers

Pipeline

Step 1: Identify Changed Files

git diff --name-only main...HEAD

If on

main

, use

git diff --name-only HEAD~5

(last 5 commits) or ask the user for the commit range.

Step 2: Launch Parallel Review Agents

Spawn agents simultaneously using the Task tool:

Agent	Type	Scope	What it checks
Security Reviewer	`security-reviewer` (custom)	Changed files only	OWASP Top 10, IDOR, injection, auth gaps
API Route Auditor	`Explore` agent	Routes + types dirs	Schema coverage, type drift, auth hooks
Scope Auditor	`Explore` agent	`git diff` output	Files modified outside task scope, formatting-only changes

Add project-specific reviewers as needed (e.g., database query reviewer, framework-specific reviewer).

Step 3: Synthesize Report

Combine all agent outputs into a single report:

## Pre-PR Review Report

### Summary
| Reviewer        | Findings | Critical | Warnings |
|-----------------|----------|----------|----------|
| Security        | 2        | 0        | 2        |
| API Audit       | 3        | 1        | 2        |
| Scope           | 1        | 0        | 1        |

### Critical Issues (must fix before merge)
[List any CRITICAL/HIGH findings]

### Warnings (consider fixing)
[List MEDIUM/LOW findings]

### Clean Areas
[List what passed review with no issues]

Step 4: Verdict

End with a clear go/no-go:

READY TO MERGE — No critical issues, warnings are acceptable
NEEDS FIXES — Critical issues found, list what must change
NEEDS DISCUSSION — Architectural concerns or ambiguous scope

Arguments

```
$ARGUMENTS
```
: Optional scope or commit range
- Example:
```
/review-all
```
  — review changes vs main
- Example:
```
/review-all HEAD~3
```
  — review last 3 commits
- Example:
```
/review-all --security-only
```
  — only security reviewer

Key Rules

Read-only — do not modify any files
Parallel execution — all agents run simultaneously for speed
De-duplicate — if two agents flag the same line, merge into one finding
No false positives — only report genuine issues with file:line references