docs-drift

# Docs Drift The third leg of the pre-release stool. `/release-status` tells you *what's queued*, `/pre-release-review` verifies *the changelog tells the truth about the code* — this skill verifies *the docs tell the truth after the change*. Changelogs are written at change time; docs are written once and rot. Every `[Unreleased]` bullet is a claim that something is now different, and each such claim can strand a doc that still describes the old world. **Read-only until the operator approves.** The audit itself never edits, commits, or tags. Proposed edits are applied only after the operator picks them in Step 5. ## Usage `/docs-drift [<plugin-slug>]` - **No arg** — audit every plugin under `plugins/*/` with a non-empty `[Unreleased]` section. Default and common case. - **`<slug>`** — narrow to one plugin (root README/CLAUDE.md still checked, but only against that plugin's changes). Natural ordering before a ship: `/release-status` (overview) → `/pre-release-review` (changelog vs code) → `/docs-drift` (docs vs changelog) → `/release <slug>`. ## Step 1 — Scope: which plugins have unreleased changes ```bash for p in plugins/*/CHANGELOG.md; do slug=$(basename "$(dirname "$p")") awk '/^## \[Unreleased\]/{f=1; next} /^## \[/{f=0} f && NF' "$p" | grep -q . \ && echo "$slug" done ``` Plugins with an empty (or absent) `[Unreleased]` are out of scope — nothing new to drift against. If nothing is in scope, say so and stop: "No unreleased changes in any plugin — nothing...