What is generate-changelog?

A command that turns Git commit history and pull requests into a formatted changelog. A changelog is a readable record of changes in each software version.

Use it to create a changelog for a target version from the latest tag or another starting tag, following common commit and changelog formats.

It removes the need to manually sort commits into added, fixed, changed, documented, and breaking changes.

generate-changelog — Command for Claude Code by TheBeardedBearSAS

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/TheBeardedBearSAS/claude-craft

Made for: Claude Code.

Or install claude-craft, the plugin that ships this one along with the rest of its 56 skills, 94 commands, 47 agents, 5 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/thebeardedbearsas/claude-craft/generate-changelog/github.svg)](https://agentmods.dev/commands/thebeardedbearsas/claude-craft/generate-changelog)

Your own site

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

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

When invoked 1,719 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.00008	$0.01719
Opus 5	$0.00004	$0.00860
Sonnet 5	$0.00002	$0.00344
Haiku 4.5	$0.00001	$0.00172

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

Security

Grade A, and why

generate-changelog 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 10d 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/common/generate-changelog.md · 238 lines

How it starts

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

Génération Automatique du Changelog

Tu es un assistant de documentation. Tu dois analyser les commits git et générer un changelog formaté selon les conventions Conventional Commits et Keep a Changelog.

Arguments

$ARGUMENTS

Arguments :

Version cible (ex: 1.2.0)
Depuis (tag précédent, défaut: dernier tag)

Exemple : /common:generate-changelog 1.2.0 v1.1.0

MISSION

Étape 1 : Récupérer les Commits

# Identifier le dernier tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")

# Lister les commits depuis le dernier tag
if [ -z "$LAST_TAG" ]; then
    git log --pretty=format:"%H|%s|%an|%ad" --date=short
else
    git log ${LAST_TAG}..HEAD --pretty=format:"%H|%s|%an|%ad" --date=short
fi

Étape 2 : Parser les Commits (Conventional Commits)

Format attendu : type(scope): description

Type	Catégorie Changelog
feat	Added
fix	Fixed
docs	Documentation
style	(ignoré)
refactor	Changed
perf	Performance
test	(ignoré)
chore	(ignoré)
build	Build
ci	(ignoré)
revert	Removed
BREAKING CHANGE	Breaking Changes

Étape 3 : Analyser les PRs (si disponible)

# Récupérer les PRs mergées
gh pr list --state merged --base main --json number,title,labels,author

Étape 4 : Générer le Changelog

Format Keep a Changelog :

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

## [{VERSION}] - {DATE}

### Breaking Changes
- **{scope}**: {description} ({author}) - #{PR}

### Added
- **{scope}**: {description} ({author}) - #{PR}
- **{scope}**: {description} ({author}) - #{PR}

### Changed
- **{scope}**: {description} ({author}) - #{PR}

### Deprecated
- **{scope}**: {description} ({author}) - #{PR}

### Removed
- **{scope}**: {description} ({author}) - #{PR}

### Fixed
- **{scope}**: {description} ({author}) - #{PR}

### Security
- **{scope}**: {description} ({author}) - #{PR}

### Performance
- **{scope}**: {description} ({author}) - #{PR}

## [{PREVIOUS_VERSION}] - {DATE}
...

[Unreleased]: https://github.com/{owner}/{repo}/compare/v{VERSION}...HEAD
[{VERSION}]: https://github.com/{owner}/{repo}/compare/v{PREVIOUS_VERSION}...v{VERSION}

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

10d ago First seen · 238 lines · 8 tokens per session scan A dd9df941ccca

Subscribe to this mod's changes

generate-changelog is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 7d ago), licensed MIT. It adds 8 tokens to every session and 1,719 once invoked, about $0.0000 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.

Claude Code Git and workflow Releases agents ai-tools bmad clean-architecture ddd

generate-changelog

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Génération Automatique du Changelog

Arguments

MISSION

Étape 1 : Récupérer les Commits

Étape 2 : Parser les Commits (Conventional Commits)

Étape 3 : Analyser les PRs (si disponible)

Étape 4 : Générer le Changelog

What this file has done since we first saw it

Other commands, from other repositories

changelog

auto-claude

ship

release-manager

release-swarm

run-release