
Review All
- 20 installs
- 22 repo stars
- Updated May 28, 2026
- acedergren/agentic-tools
review-all is a Claude Code skill that runs security, API, and scope reviewers in parallel and synthesizes a single pre-PR go/no-go report.
About
review-all is a Claude Code skill for a full-spectrum pre-PR code review. It launches security, API-route, and scope reviewers in parallel against changed files and synthesizes their findings into one report with a READY TO MERGE, NEEDS FIXES, or NEEDS DISCUSSION verdict. A developer uses it when preparing a PR or completing a phase and wanting a consolidated review. It is read-only and complements lint, typecheck, and tests rather than replacing them.
- Runs security, API-audit, and scope reviewers in parallel for a pre-PR review
- Synthesizes findings into a single go/no-go report with a clear verdict
- Read-only: never edits files, and scopes to changed files only
Review All by the numbers
- 20 all-time installs (skills.sh)
- Ranked #736 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
review-all capabilities & compatibility
- Capabilities
- security audit · api audit · scope review · review synthesis
- Works with
- github
- Use cases
- code review · security audit
- Pricing
- Free
What review-all says it does
Runs security, API audit, and scope reviewers in parallel and synthesizes findings into a single go/no-go report. Read-only — no file modifications.
Never let any reviewer edit files during this pipeline — read-only is non-negotiable.
npx skills add https://github.com/acedergren/agentic-tools --skill review-allAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 20 |
|---|---|
| repo stars | ★ 22 |
| Last updated | May 28, 2026 |
| Repository | acedergren/agentic-tools ↗ |
What it does
Run parallel security, API, and scope reviewers on a diff and synthesize a single pre-PR go/no-go report.
Who is it for?
A consolidated, read-only pre-PR review across security, API, and scope on changed files.
Skip if: Implementation or auto-remediation tasks, whole-repo reviews of narrow diffs, or replacing lint, typecheck, and tests.
When should I use this skill?
Preparing a PR or completing a phase of work and needing a full-spectrum code review.
What you get
A single synthesized review report with merged findings and a clear merge/no-merge verdict.
- synthesized pre-PR review report
- merged findings by severity
- merge verdict
By the numbers
- Runs 3 parallel reviewers (security, API audit, scope)
- Three-verdict output: ready, needs fixes, needs discussion
Files
Review All
Comprehensive pre-PR review: run specialized reviewers in parallel, synthesize into a single report. Read-only — no changes.
NEVER
- Never let any reviewer edit files during this pipeline — read-only is non-negotiable.
- Never report duplicate findings separately when two reviewers flag the same line — merge into one finding.
- Never review the whole repository when the user only changed a narrow diff — scope to changed files.
- Never use this as a substitute for lint, typecheck, or tests — it complements them, runs after them.
- Never run this for implementation tasks or auto-remediation requests — wrong tool.
Pipeline
Step 1: Identify changed files
git diff --name-only main...HEAD
# On main: git diff --name-only HEAD~5
# Or: bash scripts/detect-review-range.shStep 2: Launch parallel review agents
Spawn all agents simultaneously via Task tool:
| Agent | Type | Scope | 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 | Out-of-scope modifications, formatting-only noise |
Add project-specific reviewers as needed (DB query reviewer, framework reviewer).
Step 3: Synthesize 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)
[CRITICAL/HIGH findings with file:line references]
### Warnings (consider fixing)
[MEDIUM/LOW findings]
### Clean Areas
[What passed with no issues]Step 4: Verdict
End with one clear statement:
- READY TO MERGE — No critical issues, warnings acceptable
- NEEDS FIXES — Critical issues found; list exactly what must change
- NEEDS DISCUSSION — Architectural concerns or ambiguous scope
Arguments
- (empty): Review changes vs
main HEAD~3: Review last 3 commits--security-only: Only security reviewer
#!/usr/bin/env bash
set -euo pipefail
if git rev-parse --verify main >/dev/null 2>&1; then
git diff --name-only main...HEAD
else
git diff --name-only HEAD~5
fi
Related skills
FAQ
Does review-all modify files?
No. It is read-only; no reviewer may edit files during the pipeline.
What reviewers does it run?
A security reviewer, an API route auditor, and a scope auditor in parallel, plus optional project-specific reviewers.