New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release Announcement

by Necmttn in Necmttn/ax

Draft or revise ax release announcements and website changelog pages.

AGPL-3.0Auto-check passedDevelopment

Install Release Announcement

skills CLI
$ npx skills add Necmttn/ax --skill release-announcement -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Necmttn/ax release-announcement --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Necmttn/ax.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-announcement .claude/skills/release-announcement && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-announcement
GitHub stars
115
Token cost
~1k tokens
SKILL.md length
411 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Draft or revise ax release announcements and website changelog pages.

  • Works in 5 steps: Resolve the version and range → Map commits and files to agent sessions → Write the announcement → …
  • The user says write release notes
  • SKILL.md covers When to fire and Workflow
  • Calls bun and git

What it does

Release Announcement is an agent skill from Necmttn/ax. Draft or revise ax release announcements and website changelog pages. Triggers when the user says "write release notes", "draft release announcement", "prepare changelog", "release page", "version page", "what changed in vX.Y.Z", "generate announcement for vX.Y.Z", or asks for a release narrative. Uses Release Please range evidence, git changed files/commits, and ax sessions/recall to explain how the release got there. Do NOT trigger for ordinary commit messages or unrelated docs.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Git. The repository describes itself as: the agent experience layer · observability + memory for AI coding agents (Claude Code + Codex) · local-first, typed, yours. The licence is AGPL-3.0.

When your agent uses it

  • The user says write release notes
  • Draft release announcement
  • Prepare changelog
  • What changed in vX.Y.Z

Example prompts

  • “write release notes”
  • “draft release announcement”
  • “prepare changelog”
  • “/release-announcement”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Resolve the version and range
  2. Map commits and files to agent sessions
  3. Write the announcement
  4. Assets and rendering
  5. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit fca259c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Announcement loads about 1k tokens when it runs. Until then it costs about 127 tokens; SKILL.md has 411 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~127
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Necmttn/ax at commit fca259c, republished under its AGPL-3.0 licence (© Necmttn). 411 words, ~1,005 tokens.

Download SKILL.mdSave it as .claude/skills/release-announcement/SKILL.md (or your agent's skills folder).
name
release-announcement
description
Draft or revise ax release announcements and website changelog pages. Triggers when the user says "write release notes", "draft release announcement", "prepare changelog", "release page", "version page", "what changed in vX.Y.Z", "generate announcement for vX.Y.Z", or asks for a release narrative. Uses Release Please range evidence, git changed files/commits, and ax sessions/recall to explain how the release got there. Do NOT trigger for ordinary commit messages or unrelated docs.
role
framing

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 and files to agent sessions

Use the file list to identify touched subsystems. Use the commit list to pick important SHAs. Then query ax:

bash
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:

  • one SHA per major topic
  • one SHA near each major schema/API/CLI change
  • any SHA tied to a surprising bug fix or reversal
  • session windows around the merge/release PR if available
Show full SKILL.md (170 more words)Show less
3. Write the announcement

Replace the generated draft with a topical narrative. Keep it concise, but make it useful:

  • How we got here - the problem, decision tree, tradeoffs, and why the final shape won. Cite session/commit evidence in prose.
  • What changed - grouped by topic, not one flat commit list.
  • Example - a CLI command, config snippet, output sample, schema fragment, or before/after workflow when the release changes behavior.
  • Visual evidence - screenshot, diagram, or output capture when a UI, CLI, dashboard, TUI, or workflow is easier to understand visually.
  • Why it matters - the practical day-to-day impact.

Do not invent motivation. If ax session evidence is missing, say what the commits and changed files prove and keep the story narrower.

4. Assets and rendering

Put website-visible release images here:

text
apps/site/public/releases/assets/

Reference them from release markdown:

md
![Focused release screenshot](/releases/assets/vX.Y.Z-topic.png)

The website release renderer supports headings, lists, links, bold scopes, fenced code blocks, and images. Use those instead of hand-written HTML.

5. Verify

Run:

bash
bun run typecheck
cd site && bun run build

If the page changed, preview and smoke the specific version page:

bash
cd site
bun run preview -- --host 127.0.0.1 --port 4175

Check /changelog and /changelog/vX.Y.Z.

© Necmttn, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/release-announcement of Necmttn/ax.

Open the folder on GitHubat commit fca259c

Compare with similar skills

Release Announcement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Announcement compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Announcement this skillNecmttn/ax115—~1kAutomated safety check: PassAGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills104k2 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    104k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from Necmttn/ax

All 12 skills in this repo

  • Tune

    Necmttn/ax

    Retrospective on one coding session that proposes changes to the agent's environment (hooks, checks, steering files, tool access) and files each as an ax proposal.

    115 GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed

  • Ax Narrate

    Necmttn/ax

    Write the agent-generated narration of the current session - the reviewable story of what changed, including what never reaches a PR (user corrections, abandoned attempts, tool failures).

    115 GitHub stars~1.7k tokensUpdated 4 days ago
    Auto-check passed

  • Ax Repo

    Necmttn/ax

    Star the ax repo, file an issue / bug report, or fork-and-open-a-PR against github.com/Necmttn/ax on the user's behalf, by shelling out to the gh CLI.

    115 GitHub stars~1.8k tokensUpdated 4 days ago
    Auto-check passed

  • Retro

    Necmttn/ax

    Guided experiment-loop retrospective over the ax agent-experience graph.

    115 GitHub stars~3.5k tokensUpdated 4 days ago
    Auto-check passed

  • Retro Meta

    Necmttn/ax

    Deep retro of retros - investigation pass that surfaces improvements across older retros and the current ax setup.

    115 GitHub stars~1.8k tokensUpdated 4 days ago
    Auto-check passed

  • Setup

    Necmttn/ax

    Install + verify ax (the agent experience layer). An agent skill from Necmttn/ax.

    115 GitHub stars~2k tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Release Announcement

What does Release Announcement do?

Draft or revise ax release announcements and website changelog pages. Release Announcement is an agent skill from Necmttn/ax. Draft or revise ax release announcements and website changelog pages.

When should I use Release Announcement?

Release Announcement fits situations like: the user says write release notes; draft release announcement; prepare changelog; what changed in vX.Y.Z.

How do I install Release Announcement in Claude Code?

Run `npx skills add Necmttn/ax --skill release-announcement -a claude-code`. Or copy the skill folder (skills/release-announcement in Necmttn/ax) into .claude/skills/release-announcement in your project. Claude Code loads it when a task matches its description.

How do I install Release Announcement in Codex?

Run `npx skills add Necmttn/ax --skill release-announcement -a codex`. Or copy the skill folder (skills/release-announcement in Necmttn/ax) into .agents/skills/release-announcement in your project. Codex loads it when a task matches its description.

Can I use Release Announcement in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Necmttn/ax --skill release-announcement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-announcement, .gemini/skills/release-announcement, .github/skills/release-announcement and .opencode/skills/release-announcement in your project.

What does Release Announcement need to run?

Going by SKILL.md and its folder, Release Announcement needs the command-line tools its instructions call (bun and git).

Does Release Announcement access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release Announcement safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Announcement use?

Release Announcement is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Announcement use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Announcement?

Skills that share tags, products or a category with Release Announcement: React Router Release Notes Prep (remix-run/react-router, 57k stars), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 70k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Announcement?

Necmttn (a GitHub user) maintains it in Necmttn/ax, which has 115 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: Necmttn/ax on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.