pre-release-review

# Pre-Release Review Run this gate immediately before `$release` or `$fleet-release`. Answer: 1. What is actually shipping in each plugin? 2. Does each plugin's `[Unreleased]` changelog accurately describe that diff? 3. Per the mode picked in Step 0: does a dedicated Codex review find correctness problems in the union release window (Step 4), or is what shipped the right design for a downstream hermit (Step 3D)? Keep Steps 1–3 and 3D read-only. Do not edit changelogs, bump versions, commit, tag, or push. Step 4 may edit only when the user chose the disclosed review-and-fix mode in Step 0. ## Invocation - `$pre-release-review` — audit every plugin with commits since its own last tag. - `$pre-release-review` for one or more `<plugin-slug>`s — audit only those plugins. - Any trailing free text is the objective: it settles the Step 0 mode when it clearly names one ("design review", "run the deep pass too") and otherwise becomes the lens the verdict answers. When installed, `$release-status` is an optional lightweight precursor. `$docs-drift` is the documentation follow-up after this changelog-vs-code audit. ## Step 0 — Pick the mode Ask once, in one message, before any git work, unless the invocation already settles it. Offer three options and accept a free-text objective alongside any of them: 1. **Readiness audit** (default) — Steps 1–3. Cheap, read-only. 2. **Audit + deep correctness review** — Steps 1–4. Choosing this authorizes the Step 4 native code review (read-on...