release-notes
/release-notes
Writes release notes from merged pull requests. Use when the user asks for release notes, a changelog entry, or "what shipped".
- Author
- uniqaiapp ↗
- Repository
- skill-shrinker ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Writes release notes from merged pull requests. Use when the user asks for release notes, a changelog entry, or "what shipped".
Triggers from the description
Original author description
Writes release notes from merged pull requests. Use when the user asks for release notes, a changelog entry, or "what shipped".
How it works
- When to use
- When not to use
- Steps
- Format
- Edge cases
- Related
SKILL.md preview
---
name: release-notes
description: Writes release notes from merged pull requests. Use when the user asks for release notes, a changelog entry, or "what shipped".
---
# Release notes writer
Collect merged pull requests between two tags, group them by label, write a Markdown section for `CHANGELOG.md` or a GitHub release. Needs `gh` authenticated (`gh auth status`).
## When to use
- Release notes or a changelog entry for a version.
- What changed between two tags or commits, or since the last release.
## When not to use
- Do not use this skill to write commit messages. Use the commit-message skill instead.
- Do not use this skill for internal sprint reports; it only looks at merged pull requests.
## Steps
1. Previous tag: `git describe --tags --abbrev=0 HEAD^`, unless the user gave a range.
2. Merged PRs in range: `gh pr list --state merged --search "merged:>=<date-of-previous-tag>" --json number,title,labels,author,url --limit 200`.
3. Group by label: `feat` (Added), `fix` (Fixed), `perf` (Performance), `docs` (Documentation), `chore`/`ci` (Internal). Unlabelled go to "Other"; ask the user before publishing if that group is not empty. Several labels: first in the order feat, fix, perf, docs, chore.
4. One bullet per PR: imperative verb ("Add", "Fix", "Remove"), under 100 characters, PR number at the end as a link. Never mention the author by name; the team does not do that in public notes.
5. ALWAYS put breaking changes first, in their own "Breaking" section, even if there is only one.
6. Present the draft. Do not create the GitHub release yourself; the user publishes.
## Format
- `## [1.4.0] - 2026-03-02`, then `### Breaking`, `### Added`, `### Fixed`, `### Performance`, `### Documentation`, `### Internal`; omit empty sections.
- Do not include pull requests that only bump dependencies unless the user asks.
- Keep the whole section under 60 lines; if it is longer, collapse "Internal" into one line with a count.
- Full example: [references/example-output.md](references/example-output.md).
## Edge cases
- No previous tag: start at the first commit and say so in the notes.
- If `gh` is not authenticated, stop and tell the user; do not try to log in.
- More than 200 PRs: ask whether to split the release.
- Notes in another language: bullets in that language, headings in English.
## Related
commit-message (commit message for staged changes), pr-description (PR description from a diff).
Files in this package (2)
- SKILL.md 2 KB
- references/example-output.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · uniqaiapp/skill-shrinker | 95 | MIT |
| mono/SkiaSharp | 100 | MIT |
| niekcandaele/claude-helpers | 100 | MIT |
| kenryu42/cc-safety-net | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| openshift-pipelines/pipelines-as-code | 100 | Apache-2.0 |
| paperwingio/paperwing | 100 | Apache-2.0 |
| jelvodev/yaap | 100 | MIT |
| yearzen1/LocalSkillManager | 100 | MIT |
Database snapshot: 13.11.2026 · package version fa6f6144fbda (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100v1-changelog
Use when writing release notes from merged PRs. Triggers on "write changelog", "release notes", or "what shipped". - 100changelog
Write release notes or a CHANGELOG.md entry from git history. Use when the user says "write the changelog", "release notes for v2.3", "what changed since the last release/tag", or is preparing a release or version bump. - 85atlas-changelog
Writes what changed, from the git history and the pull requests, never from memory: a changelog entry in the project's format, the release notes for the people who use the thing, and the version the changes call for. Use for "atlas changelog", "release notes for this version",… - 100changelog-and-release-notes
Turns merged changes into a Keep a Changelog-formatted CHANGELOG entry, determines the correct Semantic Versioning bump, and writes user-facing release notes with upgrade instructions for breaking changes. Use when cutting a release, auditing an existing changelog, or setting up… - 100create-release-notes
Generate user-facing release notes when the user asks to write release notes, document a release, summarize changes for users, or prepare a changelog between versions - 90changelog-and-release
Prepare release notes, version decisions, and a change summary from verified repository history. Use when cutting a release or documenting shipped changes.