pre-release-review

# Pre-Release Review The gate you run right before `/release <slug>` or `/fleet-release`. It answers two questions the release skills assume are already true: 1. **What is actually shipping?** — the real per-plugin diff since each plugin's last tag, not what you think you changed. 2. **Do the changelogs tell the truth about it?** — every operator-visible change has a CHANGELOG line, and no line over- or under-states what the code does. Then it runs the native `/code-review high --fix` as the deep correctness pass over the current branch delta. This is a **read-only audit** for its own steps — it never bumps a version, writes a changelog, commits, or tags. `/code-review --fix` (step 4) is the one part that mutates the working tree, and only to apply review fixes. Releasing stays the operator's explicit call via `/release`. ## Usage `/pre-release-review [<plugin-slug>]` - **No arg** — sweep every plugin under `plugins/*/` that has commits since its own last tag. This is the default and the common case. - **`<slug>`** — narrow to one plugin (e.g. `/pre-release-review hermit-scribe`), useful when you already know only one plugin is shipping. Optional precursor: `/release-status` prints the pipeline table (versions, tags, commits-ahead, core-req staleness). This skill does the deep per-plugin diff + changelog audit that the table only summarizes. Run `/release-status` first if you want the one-line overview before committing to the heavier pass. ## Step 1 — Establish per-...