release-notes
v0.5.0by releasetools · author: ReleaseTools
Draft a release's changelog entry from the commits since the last tag
What release-notes does, in the publisher's words
Draft the changelog entry for a release by reading every commit since the last tag against its own diff, ruling on each one, and writing what survives to CHANGELOG.md and to a scratch file the release itself can publish.
The ruling is the point. A model asked for release notes writes them well and leaves changes out, so every commit in the range gets a row saying whether a person running the software can observe it, and the table is on the screen before a word of the entry is written.
From the project README, punctuation lightly normalized · Open the README on GitHub
- Skills
- 3
- MCP servers
- 0
- Stars
- 0
- License
- Apache-2.0
- Repo created
- 2026-08-19
- Last pushed
- 2026-10-18
- Publisher type
- Organization
- Version
- 0.5.0
Links
Skills · 3
- prepare
- release-notes
- Draft a version's changelog entry from the commits since the last tag, ruling on each commit against one test, then write it to CHANGELOG.md and to the release body file. Use before tagging a release, when asked for release notes, a changelog entry or the body of a GitHub release, when asked what c…
- write
Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
Category
Other. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.
Keywords
changelog · release-notes · keep-a-changelog · release · git · semver
Related by publisher and keywords
Cut a release: prechecks, notes, version bump, pull request, merge, tag, publish
Guard a shared resource with a distributed lock, using the mutex CLI
Generate and maintain CHANGELOG.md files from git commit history using Keep a Changelog format with semantic versioning. Creates new changelogs or appends updates to existing ones.
Release-readiness toolkit: scores your repo 0-100 via MCP, drafts audience-friendly release notes with a skill, recommends the next semantic version, and audits every agent tool call with hooks.
Release-readiness copilot: go/no-go checks, semver suggestions, changelog drafts, and guardrails for risky release commands.
Baseline maintainer dev flow as config-driven skills: create-pr (opens PRs only after a /simplify pass, a code-review self-review and the repo's format/lint/build/test pre-flight), address-review (drive the iterative response loop on bot + human PR feedback to approval, fix, push, reply to every inline thread and a PR-level summary), release (cut a versioned release: gather changes since the last tag, update notes, run the gate, bump, tag, publish), daily-changelog (one markdown file per day from merged PRs), and daily-update (runs the repo's per-day housekeeping skills and bundles their output into one PR). Also ships three PreToolUse Bash hooks: pr-template-guard (denies a gh pr create/edit whose body is missing a heading the repo's own PR template requires), skip-label-race-guard (warns when gh pr create applies the repo's review-skip label without --draft), merge-guard (warns, never denies, when a command merges a pull request), plus an opt-in PostToolUse hook, review-reply-postcondition (a review reply that claims a fix must name a commit reachable from HEAD). Reads.claude/maintainerd.json.
[](https://agentpluginsdirectory.com/plugins/release-notes)✓ Verified . We fetched the manifest from GitHub and checked it against the official Agent Plugins 1.0.0 schema at agent-plugins.org.