← ClaudeAtlas

release-noteslisted

Generate polished, user-facing release notes in Markdown for a requested release (e.g. "do this for v1.1.0"). By default it starts from the existing auto-generated GitHub release notes and post-processes them (re-orders by importance, merges multi-PR efforts, highlights the big items, drops noise) and keeps the "New Contributors" section verbatim. Alternatively, when the user explicitly says NOT to use the existing notes, it analyzes all commits/PRs merged since the previous release tag and builds the notes from scratch. Writes the notes to a Markdown file in /tmp and returns a file reference — never writes into the repository and never edits the live GitHub release.
sesori-ai/sesori_apps_monorepo · ★ 143 · Code & Development · score 76
Install: claude install-skill sesori-ai/sesori_apps_monorepo
# Release Notes Skill Generates curated, user-facing release notes in Markdown for a given release version. The output mirrors the hand-edited style the maintainer prefers: an optional **launch announcement** section, a short **Highlights** block, then per-target **App** / **Bridge** sections (subdivided into New / Improved / Fixed / Other), then the **New Contributors** section (verbatim) when the source has one. The **All PRs merged** list is not part of the output; GitHub's own release page and the Full Changelog link cover it. Write the notes to `/tmp/sesori_release_notes_<version>.md` and reply with a clickable file reference plus the short editorial summary. Do not paste the whole notes into the reply, and never write the file into the repository. The maintainer opens the file and manually pastes the result into the GitHub release once happy. **Never edit, publish, or otherwise mutate the live GitHub release.** ## Inputs - **Version (required)** — e.g. `v1.1.0`. If the user omits the `v`, normalize to `v<x.y.z>`. - **Highlight hints (optional)** — the user may volunteer domain knowledge inline, e.g. "the windows fix was fully broken before", "android login often failed". Treat these as authoritative and weave them into Highlights / phrasing. - **Availability hints (optional)** — statements such as "this feature was hidden", "it was disabled before release", or "only OpenCode works in this release" are authoritative shipping decisions. Apply the rules below without a