How do I install the Release Notes skill?

Run npx skillmds@latest add onlyterp/release-notes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Release Notes skill do?

Build human-readable release notes from a range of commits or merged PRs It is listed under Coding & Dev Tools on SkillMD.

Is Release Notes safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Notes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Notes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Notes?

OnlyTerp (@onlyterp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Notes by onlyterp — Agent Skill

Name: Release Notes
Author: OnlyTerp

File contents

release-notes — Generate Release Notes

Produce a release-notes document following the "What's New / Improvements / Fixes / Breaking / Acknowledgements" structure used by Hermes, React, VS Code, etc.

Procedure

Resolve the range:
- If range: looks like a git range (X..Y), use git log --pretty to list commits.
- Otherwise treat it as a GitHub milestone name and pull the closed PRs via github MCP.
For each commit/PR, extract:
- Type from Conventional Commits prefix (feat:, fix:, docs:, security:, perf:, refactor:, chore:)
- Scope (inside the parentheses)
- Summary (the first line after the prefix)
- Body / PR description for context
- Author + association (CONTRIBUTOR / COLLABORATOR / MEMBER)
Group:
- 🚀 What's New — all feat: with scope outside ci|deps|docs
- ⚡ Improvements — perf: and refactor:
- 🐛 Fixes — fix:
- 🔒 Security — security: + any PR labeled security regardless of prefix
- 💥 Breaking — any PR labeled breaking or any commit with !: marker
- 📚 Docs — docs:
- 🙏 Acknowledgements — list of all non-MEMBER authors
Write in plain English. For each entry, rewrite the conventional-commit summary into a reader-friendly one-liner. Example:
- Input: feat(mcp): add http transport with reconnect backoff
- Output: HTTP MCP servers now reconnect automatically with exponential backoff.
Include PR links where available: ([#1234](https://github.com/owner/repo/pull/1234))
Output as markdown, ready to paste into a GitHub release.

Example output shape

# v1.3.0 — "Thunderbolt"

## 🚀 What's New
- HTTP MCP servers now reconnect automatically with exponential backoff. ([#1234](…))
- Gemini OAuth is now a first-class provider. ([#1270](…))

## ⚡ Improvements
- 40% faster skill load via async frontmatter parsing. ([#1205](…))

## 🐛 Fixes
- Telegram voice transcripts no longer truncate at 60s. ([#1240](…))

## 🔒 Security
- Redact GitHub PATs in log output. ([#1256](…))

## 🙏 Acknowledgements
Thanks to @alice, @bob, @charlie for contributions this release.

Cron wiring

hermes cron create "0 16 * * 5" \
  "Generate release notes for origin/main..last release" \
  --skill release-notes --name weekly-release-preview --deliver telegram

---name: release-notesdescription: Build human-readable release notes from a range of commits or merged PRs---# release-notes — Generate Release NotesProduce a release-notes document following the "What's New / Improvements / Fixes / Breaking / Acknowledgements" structure used by Hermes, React, VS Code, etc.## Procedure1. **Resolve the range:** - If `range:` looks like a git range (`X..Y`), use `git log --pretty` to list commits. - Otherwise treat it as a GitHub milestone name and pull the closed PRs via `github` MCP.2. **For each commit/PR, extract:** - Type from Conventional Commits prefix (`feat:`, `fix:`, `docs:`, `security:`, `perf:`, `refactor:`, `chore:`) - Scope (inside the parentheses) - Summary (the first line after the prefix) - Body / PR description for context - Author + association (CONTRIBUTOR / COLLABORATOR / MEMBER)3. **Group:** - **🚀 What's New** — all `feat:` with scope outside `ci|deps|docs` - **⚡ Improvements** — `perf:` and `refactor:` - **🐛 Fixes** — `fix:` - **🔒 Security** — `security:` + any PR labeled `security` regardless of prefix - **💥 Breaking** — any PR labeled `breaking` or any commit with `!:` marker - **📚 Docs** — `docs:` - **🙏 Acknowledgements** — list of all non-MEMBER authors4. **Write in plain English.** For each entry, rewrite the conventional-commit summary into a reader-friendly one-liner. Example: - Input: `feat(mcp): add http transport with reconnect backoff` - Output: `HTTP MCP servers now reconnect automatically with exponential backoff.`5. **Include PR links** where available: `([#1234](https://github.com/owner/repo/pull/1234))`6. **Output** as markdown, ready to paste into a GitHub release.## Example output shape```markdown# v1.3.0 — "Thunderbolt"## 🚀 What's New- HTTP MCP servers now reconnect automatically with exponential backoff. ([#1234](…))- Gemini OAuth is now a first-class provider. ([#1270](…))## ⚡ Improvements- 40% faster skill load via async frontmatter parsing. ([#1205](…))## 🐛 Fixes- Telegram voice transcripts no longer truncate at 60s. ([#1240](…))## 🔒 Security- Redact GitHub PATs in log output. ([#1256](…))## 🙏 AcknowledgementsThanks to @alice, @bob, @charlie for contributions this release.```## Cron wiring```bashhermes cron create "0 16 * * 5" \ "Generate release notes for origin/main..last release" \ --skill release-notes --name weekly-release-preview --deliver telegram```

Frequently asked questions

Release Notes