agentmods.dev

Release Notes Generator

Release Notes Generator is a skill for Claude Code, Codex from Notysoty/openagentskills. It costs 22 tokens per session (1,218 once invoked), scanned A, original, MIT.

A writing aid that turns Git history or pull-request descriptions into release notes. Git history records code changes; release notes explain those changes to users in readable Markdown.

In plain words
What is it for?
Use it to prepare GitHub release descriptions, CHANGELOG.md files, or blog-post updates before a software release.
Why use it?
Commit messages and pull-request titles are often too technical, inconsistent, or incomplete for users. It groups related changes and rewrites them in plain language.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for cline. Also seen: mentions Claude Code; mentions Codex; built for cline.

not rated 9repo 2mo ago A scan 22 tokens original MIT

Good fit Use it to prepare GitHub release descriptions, CHANGELOG.md files, or blog-post updates before a software release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/notysoty/openagentskills/release-notes-generator
View source ↗ Notysoty/openagentskills
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.

Any agent
npx skills add Notysoty/openagentskills --skill release-notes-generator
Clone the repo
git clone --depth 1 https://github.com/Notysoty/openagentskills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Release Notes Generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/notysoty/openagentskills/release-notes-generator/github.svg)](https://agentmods.dev/skills/notysoty/openagentskills/release-notes-generator)
Your own site
<a href="https://agentmods.dev/skills/notysoty/openagentskills/release-notes-generator"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/release-notes-generator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Release Notes Generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/notysoty/openagentskills/release-notes-generator"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/release-notes-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,218 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.01218
Opus 5.5 $0.00009 $0.00487
Sonnet 5.5 $0.00004 $0.00244
Haiku 4.5 $0.00002 $0.00122

Measured 1mo ago against content hash 715a20ec4141, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Release Notes Generator 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 1mo 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/release-notes-generator/SKILL.md · 137 lines

How it starts

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

Release Notes Generator

What this skill does

This skill takes raw git log output or a list of PR titles/descriptions and turns them into polished, user-facing release notes. It groups changes by category, rewrites technical commit messages into plain English, and formats the output as clean markdown ready to paste into GitHub Releases, a CHANGELOG.md, or a blog post.

Use this before every release to save time and produce consistent, readable changelogs your users will actually understand.

How to use

Claude Code / Cline

Copy this file to .agents/skills/release-notes-generator/SKILL.md in your project root.

Then run:

git log v1.2.0..v1.3.0 --oneline

Paste the output and ask:

  • "Use the Release Notes Generator skill to turn this git log into release notes for v1.3.0."
  • "Generate release notes from these PR titles using the Release Notes Generator skill."

Cursor

Add the "Prompt / Instructions" section below to your .cursorrules file, then paste your git log or PR list into the chat.

Codex

Paste your git log or PR descriptions directly into the chat along with the instructions below. Include PR body text when available — it gives Codex more context for accurate categorization.

The Prompt / Instructions for the Agent

When asked to generate release notes, follow these steps:

  1. Parse the input. Accept any of:

    • git log --oneline output (hash + short message)
    • Full git log with commit bodies
    • A numbered or bulleted list of PR titles
    • A list of PR titles + descriptions

  2. Categorize each change into one of these buckets:

    • New Features — new capabilities, pages, commands, or options added
    • Improvements — enhancements to existing features (faster, easier to use, more options)
    • Bug Fixes — things that were broken and are now fixed
    • Breaking Changes — anything that requires users to update their code, config, or workflow
    • Security — security patches, dependency updates for known CVEs
    • Under the Hood — refactors, dependency bumps, CI changes (only include if relevant to devs)

Read the full file on GitHub · 137 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.

  1. 1mo ago First seen · 137 lines · 22 tokens per session scan A 715a20ec4141

Subscribe to this mod's changes

Release Notes Generator is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,218 once invoked, about $0.0001 per session on Opus 5.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-31.

Claude CodeGit and workflowProductivityReleasesWriting and docsagent-skillschangelogclaudeclaude-skillsclinecursordocumentation
Related

Other skills, from other repositories

publish

Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.

code-yeongyu/oh-my-openagent · 68 tokens

pre-publish-review

Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…

code-yeongyu/oh-my-openagent · 161 tokens

changelog-generator

Convierte un git log, lista de commits o notas de lanzamiento en un changelog pulido orientado al usuario. Usa cuando estés escribiendo notas de versión, generando una entrada en CHANGELOG.md o documentando qué cambió en una versión. Produce una sección de changelog estructurada con encabezado de versión, cambios…

mohitagw15856/pm-claude-skills · 96 tokens

release-notes-from-git-log

Turn a git log into user-facing release notes grouped by feature and fix. Use when asked for release notes from this git log, a changelog entry from these commits, or to turn commits into release notes. Produces a grouped changelog with one line per change and a short headline.

mohitagw15856/pm-claude-skills · 66 tokens

get-unpublished-changes

Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.

code-yeongyu/oh-my-openagent · 38 tokens

han-release

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…

testdouble/han · 172 tokens