Help us improve
Share bugs, ideas, or general feedback.
From ax
Drafts release announcements and website changelog pages grounded in git history and ax agent session evidence. Triggered by requests for release notes, changelogs, or version narratives.
npx claudepluginhub necmttn/axHow this skill is triggered — by the user, by Claude, or both
Slash command
/ax:release-announcementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write release announcements that are grounded in the actual release range and
Prepares release artifacts (PUBLIC-NOTES.md, CHANGELOG.md, summaries, migration guides) and audits readiness (blockers, docs alignment, versions, CVEs) from git ranges. Full prepare pipeline available.
Generates and manages changelogs/release notes from git history and Conventional Commits. Supports Keep a Changelog format, breaking change docs, migration guides, audience-specific notes.
Generates human-friendly changelogs from git history using ref ranges, tags, or PRs. Polishes commits, follows Keep a Changelog format, matches existing styles.
Share bugs, ideas, or general feedback.
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.
Use this skill for:
Do not use this for a single commit message, generic README edits, or a non-release feature doc.
If the version is known:
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:
BASE_REF)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:
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"
Use the file list to identify touched subsystems. Use the commit list to pick important SHAs. Then query ax:
ax ingest here --since=30d
ax sessions here --days=30
ax sessions near <important-sha>
ax recall "<subsystem or decision>" --sources=turn,commit --scope=here
For large releases, inspect at least:
Replace the generated draft with a topical narrative. Keep it concise, but make it useful:
Do not invent motivation. If ax session evidence is missing, say what the commits and changed files prove and keep the story narrower.
Put website-visible release images here:
apps/site/public/releases/assets/
Reference them from release markdown:

The website release renderer supports headings, lists, links, bold scopes, fenced code blocks, and images. Use those instead of hand-written HTML.
Run:
bun run typecheck
cd site && bun run build
If the page changed, preview and smoke the specific version page:
cd site
bun run preview -- --host 127.0.0.1 --port 4175
Check /changelog and /changelog/vX.Y.Z.