review（审查）

/review

Detects whether to review a plan or code, assembles the right panel, runs the review-fix loop.

1. Detect Mode

From args or context:

1. Explicit: /review plan or /review code — use that.
2. Plan file exists in ai-workspace/plans/ (non-.done.md) and no commits beyond main — plan mode.
3. git diff main...HEAD produces output — code mode.
4. Ambiguous — ask: "Reviewing the plan or the code?"

Optional overrides after mode:

• Round cap: default 3. "thorough" (5) or "quick" (1).
• Severity gate: default P2. "strict" (P1) or "lenient" (P3).

2. Assemble Panel

Plan mode (Step 4)

Lead: technical-editor (always). Target: the plan file.

Code mode (Step 6)

Lead: code-reviewer (always). Target: changed files (git diff main...HEAD).

Conditional reviewers (both modes)

Scan the target for signals. Add matching reviewers:

No signal match — run with lead only.

Invoke /assemble-panel if available for RETAIN, EXPAND, CONVERGE, and ESCALATE_RECURRING governance. Do not duplicate its policy algebra.

Codex/Cursor: read .agents/skills/assemble-panel/SKILL.md and apply inline.

3. Dispatch

• Plan mode: invoke /plan-review via Skill tool. Pass panel and round cap. Its internal P0 loop counts as R1.
• Code mode: dispatch panel via Agent tool. Request severity-tagged findings (P0-P3).

Untagged findings: treat as P1.

4. Loop: Fix, Record, Re-review

For each round (R1..R{cap}):

a. Triage by severity gate:

• Fix (P0 through P{gate}): fix immediately. Commit: fix: address R{N} review findings with Co-Authored-By trailer.
• Record (P{gate+1}+): record, do not fix.

b. Record below-gate findings:

• Plans: append ### Deferred Findings (R{N}) to the plan file.
• Code: gh issue create --label review-finding --title "R{N}: <summary>". Cap 10/round, 20 total. If gh unavailable, append to .branch-context.md.

c–f. Panel governance — invoke /assemble-panel for RETAIN, EXPAND, CONVERGE, ESCALATE_RECURRING.

5. Summary

Review Summary
───────────────────────────────────────
Mode:      plan | code
Target:    <file or diff summary>
Rounds:    <N of cap>
Gate:      P<N>

│ Round │ P0 │ P1 │ P2 │ P3+ │ Fixed │ Recorded │
│───────│────│────│────│─────│───────│──────────│

Verdict: APPROVE | ESCALATE

• APPROVE — all above-gate findings resolved. Next step:

- Plan mode → Build (Step 5) - Code mode → Archive (Step 7)

• ESCALATE — unresolved above-gate findings after cap. Present to human.

Guardrails

• Never modify protected files (see AGENTS.md).
• Hard max: 5 rounds even if requested higher.
• Never auto-merge or auto-approve. Produces a verdict, not an action.
• Plain text output only — cross-surface safe.

Fallbacks

• /plan-review unavailable → dispatch technical-editor + architect-reviewer directly.
• /assemble-panel unavailable → fall back to [technical-editor, code-reviewer], gate=P2, cap=3.
• gh not authenticated → degrade to .branch-context.md.
• Reviewer returns DROP → exit immediately, print summary.