What is release-notes?

A release-notes generator that turns a range of Git commits or a GitHub milestone into grouped, plain-English notes. A milestone is a GitHub label for tracking work toward a release.

Use it to produce sections for new features, improvements, fixes, security changes, breaking changes, documentation, and acknowledgements, based on commit and pull-request details.

It removes the need to manually read every commit or pull request and organize changes for readers.

release-notes — Skill by OnlyTerp

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/onlyterp/hermes-optimization-guide/release-notes

Any agent

npx skills add OnlyTerp/hermes-optimization-guide --skill release-notes

Clone the repo

git clone --depth 1 https://github.com/OnlyTerp/hermes-optimization-guide

Made for: Claude Code, Codex.

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 845 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00018	$0.00845
Opus 5	$0.00009	$0.00423
Sonnet 5	$0.00004	$0.00169
Haiku 4.5	$0.00002	$0.00085

Measured 2d ago against content hash b21de87a152b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release-notes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/dev/release-notes/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 89 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 89 lines · 18 tokens per session scan A b21de87a152b

Subscribe to this mod's changes

release-notes is a skill published in the GitHub repository OnlyTerp/hermes-optimization-guide (620 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 845 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Security Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens