release-announcementlisted

# ax:release-announcement Write release announcements that are grounded in the actual release range and the agent sessions that produced it. This skill owns the curated layer under `docs/releases/`; Release Please still owns `CHANGELOG.md`. Assumes `ax` is on PATH and the local ax database is reachable. If `ax` fails with a DB connection error, tell the user to start the repo DB and continue from git evidence only if they ask. ## When to fire Use this skill for: - "write release notes" / "draft release announcement" - "prepare changelog" / "update the website changelog" - "release page" / "version page" / "SEO release page" - "what changed in vX.Y.Z" - "generate announcement for vX.Y.Z" - "explain how we got to this release" Do not use this for a single commit message, generic README edits, or a non-release feature doc. ## Workflow ### 1. Resolve the version and range If the version is known: ```bash bun run release:announcement -- X.Y.Z ``` This drafts `docs/releases/vX.Y.Z.md` and, when the Release Please compare heading is present, embeds: - previous release tag (`BASE_REF`) - release tag or `HEAD` (`HEAD_REF`) - `git diff --name-status "$BASE_REF..$HEAD_REF"` - `git log --reverse --format='%h %cs %s' "$BASE_REF..$HEAD_REF"` If you need to inspect manually: ```bash BASE_REF=<previous-release-tag> HEAD_REF=<release-head-or-tag> git diff --name-status "$BASE_REF..$HEAD_REF" git log --reverse --format='%h %cs %s' "$BASE_REF..$HEAD_REF" ``` ### 2. Map commits an