release-notes
/release-notes
Draft release notes and a Keep-a-Changelog CHANGELOG.md section from git history — last tag..HEAD by default, grouped into Breaking/Added/Changed/Fixed/Removed/Security/Docs from Conventional Commits or, for free-form messages, from the first word ("Add", "Fix", "Remove"…); skips merges, wip, fixup! and version-bump commits, merges duplicate subjects, links PR/MR numbers and commit SHAs for GitHub and GitLab remotes, lists authors and Co-authored-by contributors, and suggests the next semver bump. Use when cutting a release, writing a GitHub release body, or starting or updating a CHANGELOG.
- Author
- binay-py ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/release-notes.mjs
What it does and when to use it
Draft release notes and a Keep-a-Changelog CHANGELOG.md section from git history — last tag..HEAD by default, grouped into Breaking/Added/Changed/Fixed/Removed/Security/Docs from Conventional Commits or, for free-form messages, from the first word ("Add", "Fix", "Remove"…); skips merges, wip, fixup! and version-bump commits, merges duplicate subjects, links PR/MR numbers and commit SHAs for GitHub and GitLab remotes, lists authors and Co-authored-by contributors, and suggests the next semver bump. Use when cutting a release, writing a GitHub release body, or starting or updating a CHANGELOG.
Triggers from the description
Original author description
Draft release notes and a Keep-a-Changelog CHANGELOG.md section from git history — last tag..HEAD by default, grouped into Breaking/Added/Changed/Fixed/Removed/Security/Docs from Conventional Commits or, for free-form messages, from the first word ("Add", "Fix", "Remove"…); skips merges, wip, fixup! and version-bump commits, merges duplicate subjects, links PR/MR numbers and commit SHAs for GitHub and GitLab remotes, lists authors and Co-authored-by contributors, and suggests the next semver bump. Use when cutting a release, writing a GitHub release body, or starting or updating a CHANGELOG.
How it works
- What it does
- How Claude should use it
- Limits
SKILL.md preview
---
name: release-notes
description: Draft release notes and a Keep-a-Changelog CHANGELOG.md section from git history — last tag..HEAD by default, grouped into Breaking/Added/Changed/Fixed/Removed/Security/Docs from Conventional Commits or, for free-form messages, from the first word ("Add", "Fix", "Remove"…); skips merges, wip, fixup! and version-bump commits, merges duplicate subjects, links PR/MR numbers and commit SHAs for GitHub and GitLab remotes, lists authors and Co-authored-by contributors, and suggests the next semver bump. Use when cutting a release, writing a GitHub release body, or starting or updating a CHANGELOG.
---
# release-notes
`scripts/release-notes.mjs` is zero-dependency Node 22+. It only reads git, except with `--write`. It never creates tags, commits or pushes.
```
node release-notes.mjs # last tag..HEAD, printed
node release-notes.mjs --version 1.4.0 # header ## [1.4.0] - today (default: ## [Unreleased])
node release-notes.mjs --from v1.2.0 --to v1.3.0
node release-notes.mjs --format github --version 1.4.0 # GitHub release body + "Full Changelog" compare link
node release-notes.mjs --version 1.4.0 --changelog CHANGELOG.md --write
node release-notes.mjs --cwd path/to/repo --repo-url none
```
The notes go to stdout; a summary goes to stderr: range, kept/skipped counts, commit style detected, link base, groups, and the **suggested bump** (major if anything is breaking, minor if anything was added, else patch, computed from the last semver tag).
## What it does
- **Range:** the latest tag reachable from `--to` up to `--to`. If `--to` is itself tagged, it describes that tag (previous tag..tag) and uses its version. No tags: the whole history, and it says so.
- **Grouping:** `feat` → Added, `fix` → Fixed, `perf` → Performance, `refactor` → Changed, `docs`, `test`, `build`/`ci`, `chore`. `type!:` or a `BREAKING CHANGE:` footer → Breaking, with the footer text under the bullet. Free-form subjects are grouped by their first word (Add/New → Added, Fix → Fixed, Remove/Delete/Drop → Removed, Update/Improve/Refactor/Rename → Changed, Docs/README → Docs); anything else lands in Changed. A leading `area: ` becomes a bold scope.
- **Skipped:** merge commits, `wip`, `fixup!`/`squash!`, "Initial commit", and subjects that are only a version (`v1.0.1`, `Bump version to 1.0.0`, `chore(release): 1.2.1`). Identical subjects are listed once.
- **Links:** from `git remote get-url origin` (https, ssh and `git@host:` forms; credentials in the URL are dropped). GitHub: `#12` → `/pull/12`. GitLab: `!7` → merge request, `#7` → issue. Other hosts get plain text.
- **`--write`:** inserts the section into the changelog below `[Unreleased]` and above the newest version, creating the file with the standard Keep-a-Changelog header if missing. It refuses if that version is already present (so re-running is a no-op), regenerates an existing `[Unreleased]` section in place, and saves `CHANGELOG.md.bak` before changing anything.
## How Claude should use it
1. Run it without `--write` and read the summary. Confirm the range and the version with the user; offer the suggested bump.
2. **Rewrite the bullets for users.** The output is commit subjects, which describe what the developer did. Turn them into what changed for the person using the project: merge related commits into one bullet, drop internal noise (refactors, CI, tests, typo fixes) unless it affects users, explain breaking changes with what to do about them, and keep the PR/commit links. Don't invent changes that aren't in the commits.
3. Show the rewritten section. Only after the user agrees, write it: run with `--write` to create the section, then edit the bullets in the file (or paste the rewritten text directly).
4. Tagging and publishing are the user's call. Give them the commands (`git tag v1.4.0 && git push origin v1.4.0`, `gh release create v1.4.0 --notes-file …`); don't run them.
## Limits
- It sees commit messages only. Squash-merged PRs show their squash subject; a PR merged with a merge commit shows its individual commits, and the merge commit (with the PR number) is skipped, so those bullets have no PR link.
- First-word grouping is a guess. "Make X faster" goes to Changed, "Handle Y" to Fixed. That is why step 2 exists.
- Contributors are git author names, not GitHub usernames, so there are no `@mentions`.
- Release date is today (override with `--date YYYY-MM-DD`). No compare-link references are added at the bottom of CHANGELOG.md.
Files in this package (2)
- SKILL.md 4 KB
- scripts/release-notes.mjs 14 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · binay-py/claude-skills | 100 | 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 76eab64f76bf (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
- 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. - 90changelog
Generates or updates CHANGELOG.md from conventional commits since the last tag, grouped into Added, Changed, Fixed, Security, Removed, with story and bug IDs linked. Use when preparing a release or when asked what changed. - 100changelog-generator
Generate or update a repository CHANGELOG.md in Keep a Changelog format from git history - grouping commits since the last tag into Added/Changed/Deprecated/Removed/Fixed/Security, rewriting them as user-facing entries, and recommending the semantic version bump. Use when… - 95prepare-release
End-to-end release automation — reads commits since last tag, infers semver bump, drafts changelog, creates release PR, merges it, waits for CI green, tags, and monitors the Docker build to completion. Use when the user says: prepare release, cut a release, bump version, create… - 100changelog-keeper
Maintains a human-readable CHANGELOG.md in Keep a Changelog format from git history, suggests the next Semantic Version from Conventional Commits, and drafts release notes. Use when the user asks to update the changelog, prepare a release, bump a version, or write release notes. - 100chamoji-release
Cut a release from git history in one command with the chamoji CLI. It picks the semver bump from the commits, adds the CHANGELOG.md section, bumps manifest versions, and makes the release commit and tag (and pushes plus a GitHub release on request). Use it whenever the user…