What is changelog-gen?

A command that updates CHANGELOG.md, the file that records changes between software releases, using the project's Git history. It groups commits by types such as features, fixes, and breaking changes.

Use it to preview or write a changelog between Git tags or commits, choose a version number, review breaking changes, and prepare a release.

It turns commit history into a release summary, reducing the manual work of tracking what changed between version tags.

changelog-gen — Command for Claude Code by fatihkan

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.

Clone the repo

git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

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/commands/fatihkan/badi/changelog-gen/github.svg)](https://agentmods.dev/commands/fatihkan/badi/changelog-gen)

Your own site

<a href="https://agentmods.dev/commands/fatihkan/badi/changelog-gen"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/changelog-gen/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/commands/fatihkan/badi/changelog-gen"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/changelog-gen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 430 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.00000	$0.00430
Opus 5	$0.00000	$0.00215
Sonnet 5	$0.00000	$0.00086
Haiku 4.5	$0.00000	$0.00043

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

Security

Grade A, and why

changelog-gen 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 9d 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.

.claude/commands/changelog-gen.md · 65 lines

What it actually says

CHANGELOG.md update command. Generates a changelog from git history grouped by conventional commit types.

Required Tools

Bash (badi changelog command invocation)
git

Procedure

Step 1: Find the Latest Tag

git describe --tags --abbrev=0

Step 2: Decide the Version Number

Ask the user for the new version:

If there are breaking changes: major (2.0.0)
If there are new features (feat): minor (1.5.0)
If only fixes: patch (1.4.3)

Step 3: Generate the Changelog with the Badi CLI

Preview (does not write):

badi changelog                              # From the latest tag to HEAD
badi changelog --from v1.0.0                # From a specific tag
badi changelog --from v1.0.0 --to v2.0.0    # Between two

Write to CHANGELOG.md:

badi changelog --write --version 1.5.0

Step 4: Manual Touch-up

After auto-generating:

Edit for reader clarity where needed
Surface the breaking changes to the top
Drop commit hashes (meaningless to users)
Reorder the categories (Added -> Fixed -> Other)

Step 5: Tag + Release

Once the changelog is ready:

git add CHANGELOG.md package.json
git commit -m "chore: vX.Y.Z release"
git tag vX.Y.Z
git push origin main --tags
gh release create vX.Y.Z --title "vX.Y.Z - Title" --notes-file RELEASE_NOTES.md

Step 6: npm Publish (if applicable)

npm publish --access public

Example

/changelog-gen              # preview
/changelog-gen 1.5.0        # write to file as v1.5.0

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.

9d ago First seen · 65 lines · 0 tokens per session scan A f0125e4baa38

Subscribe to this mod's changes

changelog-gen is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 430 tokens. 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 Code Git and workflow Releases agents ai-workflow cli developer-tools hooks

changelog-gen