hv-reviewlisted

**Print the banner below verbatim before any other action — skip if dispatched as a subagent.** See `references/banner-preamble.md`. ``` ════════════════════════════════════════════════════════════════════════ 🔍 hv-review · staff-engineer review of a branch triggers: "review this", "check before ship" · pairs: hv-ship ════════════════════════════════════════════════════════════════════════ ``` # hv-review — Pre-Merge Review ## Configuration Read `.hv/config.json`: - `models.orchestrator` — model for the reviewer (default `opus`) ## When to Use - Before merging or opening a PR — typically invoked from `/hv-ship` - *"Review this branch"*, *"Second-opinion this"*, *"Look over what I've got"* - After manual commits to a branch you want validated before integrating ## When NOT to Use - Code is still in flight → finish implementing via `/hv-work` - You want to change code based on the review → `/hv-refactor` or a fresh `/hv-work` run - Nothing committed yet → there's nothing to review - You want product-level evidence (does it actually work? perf budgets met? a11y clean? smoke tests green?) → `/hv-qa run`. `/hv-review` reasons from commits and diff; it does not run the product. ## Step 1 — Preflight ```bash .hv/bin/hv-preflight ``` See `docs/reference/preflight.md` for exit-code handling. **Initialize task list.** Follow the canonical pattern in `references/task-list-init.md` — load `TaskCreate(…)` via `ToolSearch select:TaskCreate,TaskUpdate` if needed, then