What is changelog-generator?

A tool that turns Git commit history—the record of changes made to a code project—into release notes or a CHANGELOG.md file.

Use it to create notes for a version release, date range, weekly update, Notion post, or app-store listing, grouped into features, improvements, bug fixes, and security changes.

It removes the need to read and rewrite technical commit messages by hand. It also filters out internal work such as tests and build-system changes unless requested.

changelog-generator — Skill for Claude Code and Codex by eigent-ai

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 eigent-ai/agent-skills --skill changelog-generator

Clone the repo

git clone --depth 1 https://github.com/eigent-ai/agent-skills

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/eigent-ai/agent-skills/changelog-generator/github.svg)](https://agentmods.dev/skills/eigent-ai/agent-skills/changelog-generator)

Your own site

<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/changelog-generator"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/changelog-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/changelog-generator"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/changelog-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 604 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.

Model	Per session	Once invoked
Fable 5.1	$0.00058	$0.00604
Opus 5	$0.00029	$0.00302
Sonnet 5	$0.00012	$0.00121
Haiku 4.5	$0.00006	$0.00060

Measured 11d ago against content hash cb6d278da01c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

changelog-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 11d 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/git-and-github/changelog-generator/SKILL.md · 65 lines

How it starts

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

Changelog Generator

Scans commits across a date range or version tag, categorizes changes, strips internal noise, and rewrites technical language into plain prose.

Source Repository

GitHub: ComposioHQ/awesome-claude-skills (community collection)
Install upstream: npx skills add ComposioHQ/awesome-claude-skills

`/changelog`

Point at a commit range, version tag, or time window.

Workflow:

Gather commits via git log for the requested range.
Filter out internal noise — refactors, test-only, CI/chore commits unless user wants them.
Group by type: New Features, Improvements, Bug Fixes, Security.
Rewrite each entry in user-facing language (benefits, not implementation details).
Format per Keep a Changelog or the user's style guide if provided.
Output ready-to-commit CHANGELOG.md or alternate format (Notion post, app store notes).

Grouping rules:

Commit signal	Category
`feat:`, new capability	New Features
`fix:`, regression	Bug Fixes
`perf:`, `refactor:` (user-visible)	Improvements
`security:`, CVE, auth fix	Security
`chore:`, `ci:`, `test:`	Filter out (default)

Example Prompts

Generate a changelog for commits between v1.4.0 and v1.5.0. Group by features, improvements, bug fixes, security. User-facing language.
Create release notes from commits in the past 7 days. Filter chore/ci/test. Output as a Notion-ready product update post.
Write app store release notes for iOS v3.2 since the last tag. Max 200 words. Friendly and benefit-focused.

Style Guide Support

If the user provides a style guide file, enforce:

Terminology (feature names, product voice)
Tone (formal vs casual)
Formatting (bullet vs paragraph, emoji policy)

Guardrails

Run git log in the correct repo root — confirm with user if ambiguous.
Do not invent features not present in commits.
Flag breaking changes explicitly in a dedicated section.
For app store notes, respect platform character limits.

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

11d ago First seen · 65 lines · 58 tokens per session scan A cb6d278da01c

Subscribe to this mod's changes

changelog-generator is a skill published in the GitHub repository eigent-ai/agent-skills (19 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 604 once invoked, about $0.0003 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 Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

pack-submit

Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.

aeonfun/aeon · 27 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens