review-all

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Review All

PR前全面审查

Comprehensive pre-PR review that runs specialized reviewers in parallel and synthesizes findings into a single report. Read-only — no changes.
这是一项全面的PR前审查,会并行运行专业审查Agent,并将审查结果整合为一份单一报告。仅可读——不做任何修改。

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
  • 创建PR之前
  • 完成一个工作阶段之后
  • 当你需要超越代码检查(linting)的全方位代码质量审查时

Pipeline

审查流程

Step 1: Identify Changed Files

步骤1:识别变更文件

bash
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.
bash
git diff --name-only main...HEAD
如果当前处于
main
分支,使用
git diff --name-only HEAD~5
(最近5次提交),或者向用户确认提交范围。

Step 2: Launch Parallel Review Agents

步骤2:启动并行审查Agent

Spawn agents simultaneously using the Task tool:
AgentTypeScopeWhat it checks
Security Reviewer
security-reviewer
(custom)
Changed files onlyOWASP Top 10, IDOR, injection, auth gaps
API Route Auditor
Explore
agent
Routes + types dirsSchema 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).
使用Task工具同时启动多个Agent:
Agent类型审查范围审查内容
安全审查Agent
security-reviewer
(自定义)
仅变更文件OWASP Top 10、IDOR、注入漏洞、认证缺口
API路由审计Agent
Explore
agent
路由+类型目录Schema覆盖度、类型漂移、认证钩子
范围审计Agent
Explore
agent
git diff
输出
任务范围外的修改文件、仅格式变更的内容
可根据需要添加项目专属审查Agent(例如:数据库查询审查Agent、框架专属审查Agent)。

Step 3: Synthesize Report

步骤3:整合审查报告

Combine all agent outputs into a single report:
undefined
将所有Agent的输出整合为一份单一报告:
undefined

Pre-PR Review Report

Pre-PR Review Report

Summary

Summary

ReviewerFindingsCriticalWarnings
Security202
API Audit312
Scope101
ReviewerFindingsCriticalWarnings
Security202
API Audit312
Scope101

Critical Issues (must fix before merge)

Critical Issues (must fix before merge)

[List any CRITICAL/HIGH findings]
[List any CRITICAL/HIGH findings]

Warnings (consider fixing)

Warnings (consider fixing)

[List MEDIUM/LOW findings]
[List MEDIUM/LOW findings]

Clean Areas

Clean Areas

[List what passed review with no issues]
undefined
[List what passed review with no issues]
undefined

Step 4: Verdict

步骤4:审查结论

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
结尾给出明确的可合并/不可合并结论:
  • READY TO MERGE — 无严重问题,警告可接受
  • NEEDS FIXES — 发现严重问题,列出必须修改的内容
  • NEEDS DISCUSSION — 存在架构问题或范围不明确的情况

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
  • $ARGUMENTS
    : 可选的审查范围或提交范围
    • 示例:
      /review-all
      —— 对比main分支审查变更
    • 示例:
      /review-all HEAD~3
      —— 审查最近3次提交
    • 示例:
      /review-all --security-only
      —— 仅运行安全审查Agent

Key Rules

核心规则

  1. Read-only — do not modify any files
  2. Parallel execution — all agents run simultaneously for speed
  3. De-duplicate — if two agents flag the same line, merge into one finding
  4. No false positives — only report genuine issues with file:line references
  1. 仅可读 — 不得修改任何文件
  2. 并行执行 — 所有Agent同时运行以提升审查速度
  3. 结果去重 — 如果两个Agent标记了同一行代码,将其合并为一个审查结果
  4. 无假阳性 — 仅报告带有文件:行号引用的真实问题