← ClaudeAtlas

releaselisted

Make a published GitHub Release's notes friendly — rewrite the mechanical, one-line-per-PR changelog body into autonomOS's themed/emoji format (the v0.3.0 style Terry approved). Use when asked to "make the release notes friendly", "theme the release body", "prettify the release notes", or generate the friendly release notes for a version. Reads the mechanical body from scripts/release-notes.ts, regroups the PRs into themed sections, and applies the result via `gh release edit`. Does NOT cut releases or edit CHANGELOG.md.
aterrylu/autonomOS · ★ 6 · AI & Automation · score 71
Install: claude install-skill aterrylu/autonomOS
# /release — friendly release-notes rewrite autonomOS ships release notes in **two layers** (see ADR-044): - **Floor of correctness** — the mechanical, one-line-per-PR body that `scripts/sync-changelog.ts` consolidates into `CHANGELOG.md` and `scripts/release-notes.ts` extracts. CI publishes this automatically. It is always correct and never themed. - **Ceiling of friendliness** — the themed/emoji body Terry approved for `v0.3.0`. **That is what this skill produces.** This skill is the ceiling. The model doing the rewrite is **the Claude Code session running this skill** — there is no API key, no Anthropic SDK call, and no CI step. You read the mechanical body, transform it, and apply it to the live release. Because the mechanical floor already shipped from CI, this is a safe, reversible *enhancement* of an already-correct release body. > **The spec is [`canonical-example.md`](./canonical-example.md).** Read it in full > before writing anything. It is the exact `v0.3.0` mechanical→friendly pair. Match > its structure, density, and tone. Do not try to be cleverer than the example — > consistency with it IS the goal. **Preconditions:** `gh` must be authenticated (`gh auth status`) and `bun` available. If `gh` isn't logged in, step 1's commands fail with an auth error — that is an auth problem, NOT a missing release; don't tell the user to publish one. --- ## Procedure ### 1. Determine the version and tag - If the user gave a version/tag, use it. Otherwise deriv