workbench-review-qa

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Workbench Review QA

Workbench评审QA

Use this skill for code review, workflow review, QA verification, release checks, and issue closeout.

本技能适用于代码评审、工作流评审、QA验证、发布检查及问题收尾。

Verdicts

评审结论

```
PASS
```
: objective is met and evidence is sufficient.
```
FLAG
```
: useful progress, but a non-blocking issue or missing evidence remains.
```
BLOCK
```
: objective is not met, unsafe, unverifiable, or materially wrong.

```
PASS
```
：已达成目标，且证据充分。
```
FLAG
```
：取得了有效进展，但存在非阻塞性问题或证据缺失。
```
BLOCK
```
：未达成目标、存在安全问题、无法验证或存在实质性错误。

Review Method

评审方法

Identify the promised objective.
Inspect the real output, diff, issue comments, runtime state, or checked-out repo.
Compare evidence against the objective.
Verify the smallest real path that proves the claim.
Report findings first, ordered by severity.
Check command syntax and live-resource ownership when the work involves Multica CLI mutations.
If duplicate comments or artifacts exist, identify the primary artifact and explain why.
For
```
GOAL_MODE: yes
```
or
```
/goal
```
work, compare the closeout against the locked objective and every required closeout gate.

明确既定目标。
检查实际输出、差异（diff）、问题评论、运行时状态或已检出的代码仓库（repo）。
将证据与目标进行比对。
验证能够证明结论的最简实际路径。
优先按严重程度排序报告发现的问题。
当工作涉及Multica CLI变更时，检查命令语法及实时资源归属。
若存在重复评论或工件，确定主工件并说明原因。
对于
```
GOAL_MODE: yes
```
或
```
/goal
```
任务，将收尾结果与锁定目标及所有要求的收尾关卡进行比对。

Findings Format

发现结果格式

For problems, return:

severity,
location or evidence,
why it matters,
required fix or next verification.

For clean reviews, return:

verdict,
```
VERDICT_SUMMARY
```
: three lines or fewer,
evidence checked,
residual risk or test gap.

Every SDD review should include

VERDICT_SUMMARY

so the next agent can continue from the review header without re-reading the full review body.

若发现问题，需返回：

严重程度，
位置或证据，
问题影响，
所需修复措施或下一步验证内容。

若评审无问题，需返回：

评审结论，
```
VERDICT_SUMMARY
```
：不超过三行，
已检查的证据，
剩余风险或测试缺口。

所有SDD评审均需包含

VERDICT_SUMMARY

，以便后续Agent无需通读完整评审内容即可从评审标题处继续工作。

Auto Review Sweeper

自动评审扫查器

For automatic

in_review

handoffs, use this exact block on each reviewed target:

text

AUTO_REVIEW
TARGET: <identifier>
VERDICT: PASS | FLAG | BLOCK
VERDICT_SUMMARY: three lines or fewer
EVIDENCE: concrete issue/comment/run IDs, commands, or file paths checked
STATUS_ACTION: done | kept in_review | blocked | no_change
NEXT_ACTION: exact next owner/action, or none

```
PASS
```
may move the target issue to
```
done
```
only when the original goal is satisfied and no required follow-up remains.
```
FLAG
```
leaves the issue in
```
in_review
```
with a bounded next action.
```
BLOCK
```
sets the issue to
```
blocked
```
with blocking evidence.
If evidence is still arriving, leave the issue unchanged and mark it pending in the sweep summary.

对于自动

in_review

交接，需对每个评审目标使用以下格式块：

text

AUTO_REVIEW
TARGET: <identifier>
VERDICT: PASS | FLAG | BLOCK
VERDICT_SUMMARY: three lines or fewer
EVIDENCE: concrete issue/comment/run IDs, commands, or file paths checked
STATUS_ACTION: done | kept in_review | blocked | no_change
NEXT_ACTION: exact next owner/action, or none

仅当原始目标已达成且无后续必要工作时，
```
PASS
```
可将目标问题标记为
```
done
```
。
```
FLAG
```
将问题保留在
```
in_review
```
状态，并明确下一步操作。
```
BLOCK
```
将问题标记为
```
blocked
```
状态，并附上阻塞证据。
若证据仍在收集，保持问题状态不变，并在扫查总结中标记为待处理。

QA Rules

QA规则

Do not accept
```
done
```
based on paraphrase alone.
Distinguish content failures from workflow/tooling failures.
If repo access is needed, prefer the issue's project-bound GitHub repo resource and report the commit/branch inspected.
For Goal Mode tasks,
```
PASS
```
requires evidence for the locked objective plus all relevant build/test/help-smoke/docs-or-report/git-status gates, or an explicit rationale for each non-applicable gate.
Treat
```
file://<LOCAL_WORKBENCH_REPO>
```
as laptop-local fallback only; remote runtimes must flag it as invalid unless explicitly mounted.
Keep evidence concise and reproducible.
Verify
```
Workbench Max
```
remains untouched when a task says it must be preserved.

不得仅基于转述就接受
```
done
```
状态。
区分内容故障与工作流/工具故障。
若需访问代码仓库（repo），优先使用问题关联项目的GitHub仓库资源，并报告已检查的提交（commit）/分支（branch）。
对于Goal Mode任务，
```
PASS
```
要求提供锁定目标的证据，以及所有相关的构建/测试/help-smoke/文档或报告/git状态关卡的证据，或针对每个不适用关卡提供明确理由。
仅将
```
file://<LOCAL_WORKBENCH_REPO>
```
视为本地笔记本电脑的备选方案；远程运行时必须将其标记为无效，除非已明确挂载。
保持证据简洁且可复现。
若任务要求保留
```
Workbench Max
```
，需确认其未被改动。