A command that builds a changelog, a list of changes in a software release, from Git commits since the last release tag.

Use it to prepare release notes grouped into sections such as Added, Fixed, Documentation, and Maintenance.

It removes the need to read and sort commit history by hand. It also suggests a version number from the commit types and flags breaking changes.

changelog — Command for Claude Code by kid-sid

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/kid-sid/claude-spellbook

Made for: Claude Code.

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/kid-sid/claude-spellbook/changelog/github.svg)](https://agentmods.dev/commands/kid-sid/claude-spellbook/changelog)

Your own site

<a href="https://agentmods.dev/commands/kid-sid/claude-spellbook/changelog"><img src="https://agentmods.dev/badge/commands/kid-sid/claude-spellbook/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/kid-sid/claude-spellbook/changelog"><img src="https://agentmods.dev/badge/commands/kid-sid/claude-spellbook/changelog.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 603 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.00603
Opus 5	$0.00000	$0.00302
Sonnet 5	$0.00000	$0.00121
Haiku 4.5	$0.00000	$0.00060

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

Security

Grade A, and why

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 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.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.

Generate a changelog from git history since the last release tag.

Instructions

Find the last release tag:
```
git describe --tags --abbrev=0
```
If no tags exist, use the first commit: git rev-list --max-parents=0 HEAD

Get all commits since that tag:

git log <last-tag>..HEAD --pretty=format:"%H %s" --no-merges

If a specific version argument was provided by the user (e.g. v1.3.0), use that as the new version. Otherwise, infer the next version by incrementing the last tag:
- Any feat: commit → bump minor (e.g. v1.2.0 → v1.3.0)
- Only fix: / chore: / docs: → bump patch (e.g. v1.2.0 → v1.2.1)
- Breaking change (feat!: or BREAKING CHANGE: in body) → bump major
Group commits by conventional commit type:

Prefix Changelog section

feat: / feat!: Added

fix: Fixed

docs: Documentation

refactor: Changed

perf: Performance

chore: / ci: / build: Maintenance

revert: Reverted

Discard commits without a conventional prefix (unless they're meaningful — use judgment).
For each commit, strip the type prefix and capitalise the first letter. Include the short SHA as a link reference if on GitHub (use git remote get-url origin to determine the base URL).
Output the changelog block in Keep a Changelog format:

Prefix	Changelog section
`feat:` / `feat!:`	Added
`fix:`	Fixed
`docs:`	Documentation
`refactor:`	Changed
`perf:`	Performance
`chore:` / `ci:` / `build:`	Maintenance
`revert:`	Reverted

## [<version>] - <YYYY-MM-DD>

### Added
- Short description of feature (#sha)

### Fixed
- Short description of fix (#sha)

### Changed
- Short description of refactor (#sha)

### Maintenance
- Short description of chore (#sha)

If CHANGELOG.md exists in the repo root, prepend the new block after the # Changelog header (or at the top if no header). Show the user the final result and ask whether to write it to the file.
If CHANGELOG.md does not exist, output the block only — do not create the file unless the user asks.

Notes

Omit sections with no entries.
If the commit range is empty (no commits since last tag), say so and stop.
Do not include merge commits.
Breaking changes get a > ⚠ Breaking change: callout under the relevant entry.

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.

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

Subscribe to this mod's changes

changelog is a command published in the GitHub repository kid-sid/claude-spellbook (188 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 603 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-30.

Git and workflow Releases

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

ship

Ship is the operational release-prep flow for a connected project repo.

robotaitai/project-bedrock · 0 tokens

release-plan

A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.

alisunstar/OpenSunstar · 0 tokens

release

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

terrene-foundation/kailash-coc-claude-py · 0 tokens

create-pr

Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.

dsswift/ion · 25 tokens