Back to Details

review-verify

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Review Verify (internal)

审核验证（内部）

Composed by 
review-change
/ 
product-audit
within their conversation — on any agent, follow this file inline as the routed step. Findings only; never edits, never refactors.
由对话过程中的
review-change
/ 
product-audit
组合而成——针对任意Agent，需按照本文件内容执行该路由步骤。仅记录发现问题；绝不编辑、重构代码。

Scope

范围

The diff or path/glob the caller passes; default the current change vs the default branch. State the scope at the top of the returned table.
调用者传入的差异内容或路径/通配符；默认对比当前变更与默认分支。需在返回表格顶部说明范围。

Checklist (evaluate EVERY item — none is optional; n/a must be stated)

检查清单（需评估每一项——无可选项；不适用需明确说明）

✓ The project's verification gate ran in THIS review (type-check, tests, build per the project's declared commands) — paste exit status per command ✓ The change's primary claimed behavior was exercised for real (run the CLI/endpoint/function; paste the actual observed output) ✓ At least one failure-mode from the SPEC's dev scenarios was reproduced (bad input, missing file, error path) and behaved as specified ✓ New/changed tests actually fail when the implementation is reverted or broken (mutate or stash to prove they assert something — restore after) ✓ No test was skipped/disabled to get green (grep for skip/only/todo markers in the diff) ✓ The build artifact/dev server starts cleanly (no new warnings that indicate breakage) ✓ Anything that can only be confirmed by a human (visual, device, locale, load) is listed explicitly under "Manual" — never silently dropped
✓ 本次审核中已运行项目的验证关卡（根据项目声明的命令执行类型检查、测试、构建）——粘贴各命令的退出状态 ✓ 已实际验证变更的核心预期行为（运行CLI/端点/函数；粘贴实际观测到的输出） ✓ 已重现SPEC开发场景中的至少一种故障模式（错误输入、文件缺失、错误路径），且行为符合规范要求 ✓ 当实现被回滚或破坏时，新增/修改的测试确实会失败（通过修改或暂存代码来证明测试有实际断言——之后恢复） ✓ 未通过跳过/禁用测试来获得绿态（在差异内容中搜索skip/only/todo标记） ✓ 构建产物/开发服务器可正常启动（无表明存在故障的新警告） ✓ 所有只能由人工确认的内容（视觉效果、设备、区域设置、负载）均明确列在“人工检查”下——绝不忽略

Return exactly

返回格式严格如下

REVIEW VERIFY — scope: <scope>

| # | Finding | Sev | Evidence | Suggested fix |
|---|---------|-----|----------|---------------|
| 1 | <what>  | critical|major|minor | <file:line> | <smallest action> |

Checklist: <n> evaluated, <n> pass, <n> findings, <n> n/a (<which + why>)
Summary: <1-2 sentences>
Manual (a human must check): <bullet list, or "none">
Decision: PASS | FAIL
FAIL if any critical or major finding is open; PASS otherwise. Minor findings never block — they route to the caller's triage step.
REVIEW VERIFY — scope: <scope>

| # | Finding | Sev | Evidence | Suggested fix |
|---|---------|-----|----------|---------------|
| 1 | <what>  | critical|major|minor | <file:line> | <smallest action> |

Checklist: <n> evaluated, <n> pass, <n> findings, <n> n/a (<which + why>)
Summary: <1-2 sentences>
Manual (a human must check): <bullet list, or "none">
Decision: PASS | FAIL
若存在未解决的严重（critical）或主要（major）问题则判定为FAIL；否则为PASS。次要（minor）问题不会阻碍流程——它们将被路由至调用者的分类处理步骤。

Done when

完成标准

  • Every checklist item was evaluated with evidence (file:line or command output) or explicitly marked n/a with the reason.
  • The fixed-format block above is returned — nothing more, nothing less — and no code was changed.
  • 所有检查清单条目均已通过证据（文件:行号或命令输出）完成评估，或已明确标记为n/a并说明原因。
  • 返回上述固定格式的内容——不多不少——且未修改任何代码。