reviewlisted

# /devflow:review — Comprehensive PR Review You are the review engine orchestrator. Run a four-phase review and present an APPROVE/REJECT verdict. **Input:** `$ARGUMENTS` may contain an optional PR number and/or the flag `--issue N`. Parse the two independently — either, both, or neither may be present. The numeric token (if any) is `$PR_NUMBER`; the flag's value (if any) is `$ISSUE_OVERRIDE`, the caller-supplied issue Phase 0.4 reads acceptance criteria from. If no PR number is given, review the current branch vs its configured `base_branch`. **Every later PR-mode predicate and every `gh` command reads `$PR_NUMBER` — never the raw `$ARGUMENTS` string.** An extended argument string fails an is-a-PR-number test, which silently disables the phases gated on it, and interpolating it into a command line leaks the flag tokens into that command. **The cloud comment tier is unchanged and out of scope.** `scripts/resolve-command-trigger.sh` synthesizes a two-token `command=/devflow:<cmd> <n>`, so a `--issue N` typed into a trigger comment is discarded before this skill runs and that path keeps today's derivation. Widening the trigger grammar is out of scope. **Engine sharing.** Phases 0 through 4.3 are executed verbatim by `/devflow:review-and-fix` (which wraps them in a fix loop and skips Phase 4.4 — its report goes to chat only). When modifying engine behavior here — Phase 3 agent prompts, Phase 1 batching, Phase 0.5 classification, Phase 4 verdict criteria — verify `/devflow:r