dispatching-code-reviewlisted

# Dispatching a Code Review **Render before asking.** Before any AskUserQuestion, render the decision context as assistant chat text. Content that exists only in a Read result, a subagent/Agent return, or the question/option strings **does not count as rendered** (the UI shows a compact card) — restate it in chat first. The companion to `dispatching-spec-review`. Spec review answers *"is what was asked delivered?"*; code review answers *"is what was delivered any good?"*. Same fresh-context subagent pattern, different concern set. ## When to Invoke | Caller | Scope | Trigger | |---|---|---| | `/ship-execute` post-task gate | One task | Optional — fires only when `effort: M\|L\|XL`; effort: S skips both spec and code review | | `/ship-execute` wave VERIFY | Wave-level diff | Optional — fires when wave touched security-relevant, financial-domain, **or database/persistence** code (migrations, schema, queries, repositories) | | `/ship-review` | Sprint or feature | **Required** before user approval | | `/ship-quick` | Single-change diff | Optional flag (`--review`) | Code review is more expensive than spec review (broader concern surface). `/ship-review` runs it mandatorily before approval; the post-task path remains optional and gated on effort. ## Inputs - `scope` — `"task" | "wave" | "feature" | "sprint"` - `target_ids` — list of task / feature IDs (or null when scope is sprint). - `base_ref` / `head_ref` — diff range. - `concerns` — subset of `["security", "bugs", "sile