Back to Details

review-team

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Review Team

审查团队

Run a fleet of specialized reviewer subagents against the same change. Each reviewer is intentionally unaware of the others and must stay within its assigned focus area.
Reviewer prompts live in 
reviewers/
. Read only the reviewer files you plan to launch.
针对同一变更运行一组专业的审查子Agent。每个审查Agent会被刻意设置为不知道其他Agent的存在，且必须严格在其指定的专注领域内开展工作。
审查提示语存储在
reviewers/
目录下。仅读取你计划启动的审查Agent对应的文件。

Modes

模式

  • single: Default. Launch reviewers once, aggregate findings, deduplicate, and report the final review.
  • iterate: Launch reviewers, fix accepted findings, rerun relevant reviewers, and repeat until the review is clean or the remaining findings are intentionally deferred.
If the user does not specify a mode, use single. Use iterate only when the user explicitly asks to keep fixing, make reviewers happy, or run until clean.
  • single（单次模式）：默认模式。启动审查Agent一次，汇总审查结果、去重后提交最终审查报告。
  • iterate（迭代模式）：启动审查Agent，修复已确认的问题，重新运行相关审查Agent，重复此过程直至审查无问题，或剩余问题被明确标记为暂缓处理。
若用户未指定模式，则使用single模式。仅当用户明确要求持续修复、让审查Agent满意，或运行至无问题时，才使用iterate模式。

Reviewer Set

审查Agent集合

Core reviewers:
  • reviewers/correctness-reviewer.md
  • reviewers/security-abuse-reviewer.md
  • reviewers/architecture-reviewer.md
  • reviewers/code-quality-conventions-reviewer.md
  • reviewers/simplicity-scope-reviewer.md
Specialist reviewers:
  • reviewers/product-ux-accessibility-reviewer.md
  • reviewers/performance-reliability-reviewer.md
  • reviewers/telemetry-observability-reviewer.md
  • reviewers/testing-strategy-reviewer.md
  • reviewers/api-compatibility-reviewer.md
  • reviewers/documentation-dx-reviewer.md
Default to all reviewers when the user asks for the full team. For narrower requests, launch only the relevant reviewers.
核心审查Agent：
  • reviewers/correctness-reviewer.md
  • reviewers/security-abuse-reviewer.md
  • reviewers/architecture-reviewer.md
  • reviewers/code-quality-conventions-reviewer.md
  • reviewers/simplicity-scope-reviewer.md
专业审查Agent：
  • reviewers/product-ux-accessibility-reviewer.md
  • reviewers/performance-reliability-reviewer.md
  • reviewers/telemetry-observability-reviewer.md
  • reviewers/testing-strategy-reviewer.md
  • reviewers/api-compatibility-reviewer.md
  • reviewers/documentation-dx-reviewer.md
当用户要求完整审查团队时，默认启用所有审查Agent。对于更具体的请求，仅启动相关的审查Agent。

Launch Pattern

启动模式

For each reviewer subagent, provide:
  1. The exact reviewer prompt from its Markdown file.
  2. The task description, PR/issue context, or user request.
  3. The diff or changed files to review.
  4. Any test results, logs, screenshots, or relevant repository context.
Add this wrapper to every reviewer prompt:
text
You are one reviewer in a fleet of independent code review agents. You cannot see the other reviewers. Stay strictly within your assigned role. Return only concrete, actionable findings with file and line references. If you find no issues in your area, say so clearly. Do not provide general commentary, praise, summaries, or duplicate concerns outside your mandate.
Prefer running independent reviewers in parallel. Do not ask multiple reviewers to solve the same broad task in the same way; their reviewer prompt is their boundary.
为每个审查子Agent提供以下内容：
  1. 其Markdown文件中的准确审查提示语。
  2. 任务描述、PR/问题上下文或用户请求。
  3. 待审查的差异文件或变更文件。
  4. 任何测试结果、日志、截图或相关仓库上下文。
为每个审查提示语添加以下包装内容：
text
You are one reviewer in a fleet of independent code review agents. You cannot see the other reviewers. Stay strictly within your assigned role. Return only concrete, actionable findings with file and line references. If you find no issues in your area, say so clearly. Do not provide general commentary, praise, summaries, or duplicate concerns outside your mandate.
优先并行运行独立审查Agent。不要让多个审查Agent以相同方式解决同一宽泛任务；它们的审查提示语就是其工作边界。

Aggregation

结果汇总

After reviewers finish:
  1. Merge duplicate findings.
  2. Drop findings that lack a concrete failure mode, user impact, security risk, or maintenance cost.
  3. Resolve conflicts using the codebase, tests, and stated requirements as evidence.
  4. Rank findings by severity and practical importance.
  5. Present findings first, with file and line references.
The final review should not expose raw reviewer transcripts unless the user asks for them.
审查Agent完成审查后：
  1. 合并重复的审查结果。
  2. 删除缺乏具体故障模式、用户影响、安全风险或维护成本的结果。
  3. 以代码库、测试和既定需求为依据解决结果中的冲突。
  4. 按严重程度和实际重要性对审查结果进行排序。
  5. 先展示带有文件和行号引用的审查结果。
最终审查报告不应暴露审查Agent的原始对话记录，除非用户明确要求。

Iterate Mode

迭代模式

In iterate mode:
  1. Run the initial reviewer set.
  2. Decide which findings are valid and should be fixed.
  3. Implement fixes directly.
  4. Run tests or checks appropriate to the changes.
  5. Rerun only the reviewers relevant to the changed areas or unresolved findings.
  6. Continue until no actionable findings remain, or until any remaining findings are explicitly documented as out of scope, false positives, or accepted tradeoffs.
Keep the user informed between iterations. Do not loop indefinitely; stop when additional iterations are not producing material new findings.
在iterate模式下：
  1. 运行初始审查Agent集合。
  2. 确定哪些审查结果有效且需要修复。
  3. 直接实施修复。
  4. 运行与变更对应的测试或检查。
  5. 仅重新运行与变更区域或未解决问题相关的审查Agent。
  6. 持续此过程直至无需要处理的审查结果，或剩余结果被明确记录为超出范围、误报，或已接受的权衡方案。
在每次迭代之间向用户通报进展。不要无限循环；当额外迭代无法产生实质性新结果时停止。

Final Response

最终响应

For single mode, return the aggregated review.
For iterate mode, return:
  • What was fixed.
  • What verification ran.
  • Which reviewers were rerun.
  • Any remaining findings or accepted tradeoffs.
对于single模式，返回汇总后的审查报告。
对于iterate模式，返回以下内容：
  • 已修复的问题。
  • 已执行的验证操作。
  • 重新运行的审查Agent。
  • 任何剩余的审查结果或已接受的权衡方案。