Code review

verify-code-review workflow (v3)

Overview

1-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — code-review 多 agent 并行" 章节 onto harnessed runtime (Phase v3.0-3.4 W0.11 — D-04 Stage ④ Verify 7 sub + 子任务并行 机制 subagent default routing 机器化 + Pattern A sub-workflow ship)。

phase	id	upstream	model	capability	parallelism
1	01-code-review	mattpocock-skills	sonnet	{{ capabilities.code-review.cmd }}	judgments.parallelism-gate.subagent-default.fires

Per-phase config loads from workflows/verify/code-review/workflow.yaml; engine spawns multiple subagent in parallel fan-out (bundled subagent-default rule — Task / Agent 工具 spawn 多任务并发, context 隔离, summary 折叠回主 context)。

Capability refs

Sister workflows/capabilities.yaml entries:

• code-review — Bucket 1 mattpocock 高频招式 (impl: mattpocock-skills, cmd: /code-review)

Parallelism gate ref

Sister workflows/judgments/parallelism-gate.yaml:

• subagent-default.fires — subtask.parallel_count <= 3 and subtask.communication_needed == false (默认 fan-out, focused 任务 research / verify / review 单文件 / 跑测试 / 抓 doc / 探索模块)

Routing rules

总 fire 当 phase.stage == 'verify' 后必跑串行 (verify-progress) 之后并行 fan-out。无 skip 条件 — code-review 多 agent 是 verify-work 第 3 phase 默认 fan-out (sister CLAUDE.md verbatim)。

How to invoke

!harnessed checkpoint intent verify-code-review

The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: the steps below (prompt → spawn → checkpoint complete) resolve it, and a per-turn <workflow-intent> reminder persists until they run.

The numbered sequence below is the state machine — execute it with Bash. Do NOT improvise an equivalent flow from the Overview above: freelancing bypasses the engine (no ledger, no evidence guard). harnessed gives you the spawn-ready prompt; YOU spawn the subagent with a CC-native Task / Agent tool (keeps the session responsive + lets clarification round-trips reach the user).

Do NOT pipe to harnessed run verify-code-review — that is the CI/headless path (in-process SDK spawn that blocks the session inside Claude Code).

1. Bash: harnessed prompt verify-code-review --task "$ARGUMENTS" --json → parse {prompt, max_iterations, model}.
2. Spawn a CC-native subagent (Task / Agent tool) with that prompt + model, wrapped in the ralph-loop plugin: /ralph-loop "<prompt>" --max-iterations <max_iterations> --completion-promise "COMPLETE". If the plugin is absent, use the native goal gate instead (Claude Code 2.1.139+ / Codex): /goal "this subtask is delivered: the subagent's final output contains verbatim <promise>COMPLETE</promise>; or stop after <max_iterations> turns" then spawn the subagent and let the goal evaluator drive re-spawns until it clears. If /goal is unavailable too, self-loop: spawn → check output for <promise>COMPLETE</promise> → re-spawn with prior output appended (up to max_iterations). Set the goal only at the leaf subtask level — /goal is single-slot per session and a nested goal overwrites the outer one.
3. If the output contains STATUS: NEEDS_CLARIFICATION + a question list: STOP, relay them verbatim via AskUserQuestion, append the answers to the spec, then re-spawn the same sub.
4. On <promise>COMPLETE</promise>: Bash harnessed checkpoint complete verify-code-review --summary "<one-line>". The evidence guard runs here (fail-CLOSED): if a declared artifacts_expected file is missing it exits non-zero — re-spawn to produce it before treating the sub as done.

<!-- harnessed-generated:v4.9.3 -->

References

• D-04 Stage ④ Verify 7 sub 分解
• workflows/capabilities.yaml — code-review
• workflows/judgments/parallelism-gate.yaml — subagent-default.fires
• workflows/defaults.yaml — ralph_max_iterations.verify-code-review.* values (W2.2 backfill)
• workflows/verify-work/workflow.yaml v2 SHIPPED phase 03-code-review-parallel sister verbatim