Skip to main content

subagent

changelog-generator — Claude Code subagent: changelog from git history

A subagent that turns git commits into a CHANGELOG.md and release notes, sorting changes by Conventional Commits. Handy right before you tag a version.

Install into Claude Code · claude-code-templates All methods and platforms ↓

npx claude-code-templates@latest --agent documentation/changelog-generator

What changelog-generator does

The subagent walks your git history and sorts commits into breaking changes, features, fixes and internal work. Parsing relies on Conventional Commits, so vague commit messages will not make it into a tidy summary. Breaking changes and migrations come first in the output.

Its toolset is small: Read, Write, Edit and Bash. It runs git itself, writes new files and edits an existing CHANGELOG.md. Output follows Keep a Changelog, with dates and version links. Beyond the changelog file it produces release notes with download links, migration guides for breaking changes, and scripts that generate the changelog automatically.

The author expects you to review the result: automate the generation, then curate the content. On a repo where commit messages follow no convention, expect little value until you agree on a template.

What it helps with

build a CHANGELOG.md from commit history
write release notes that highlight user-facing impact
document a migration path for breaking changes
group commits by category and impact
set up commit message templates and a release workflow

Example prompts for the agent

Build a CHANGELOG.md from the commits in the last release
Draft release notes for 2.0 and put breaking changes at the top
Write a migration guide for the changes in the recent commits

How to install changelog-generator

1claude-code-templates

npx claude-code-templates@latest --agent documentation/changelog-generator

2Manually: put the files in place

.claude/agents/changelog-generator.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Manually: put the files in place

.codex/agents/changelog-generator.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Manually: put the files in place

.cursor/agents/changelog-generator.md

Cursor also reads .claude/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about changelog-generator

How do I install changelog-generator in Claude Code?

Run npx claude-code-templates@latest --agent documentation/changelog-generator; the agent lands at .claude/agents/changelog-generator.md.

What does changelog-generator do?

It generates a changelog and release notes from git history, groups changes by user impact, and prepares migration guides.

Which tools does the subagent have?

Read, Write, Edit and Bash — enough to read the repo, call git and write files.

Similar subagents

All subagents for Git and GitHub →

changelog-automation Seth Hobson This skill helps generate changelogs and release notes from commits, PRs, and releases. Use it when setting up release workflows or shared commit rules. CX Codex 13,733installs deployment-engineer VoltAgent Community Designs and tunes CI/CD pipelines, automates rollback triggers, and sets up canary or blue-green releases. Helpful when manual deployment steps slow down your team. 6,079installs launchdarkly-flag-cleanup official github Checks LaunchDarkly feature flags via an MCP server, finds the safe production value, and removes dead code branches before opening a cleanup PR. 171installs pr-test-analyzer official Anthropic This subagent checks whether pull request tests cover changed behavior, edge cases, and error paths. Run it after a PR update or before sending the PR for review. ★ 44,770repo stars Technical Debt Remediation Plan official github Generates actionable technical debt remediation plans for code and test suites. It helps teams audit accumulated debt without modifying project files. ★ 40,451repo stars TDD Red Phase - Write Failing Tests First official github This subagent pulls GitHub issue context from branch names and creates failing tests for acceptance criteria before code is written. It enforces the red stage of TDD. ★ 40,451repo stars

From the same set361

The whole set →

generate-api-documentation Scans source code for endpoint annotations and builds API documentation. Supports Swagger UI, Redoc, Postman collections, and automated CI/CD steps. 1,849installs cli-ui-designer Designs terminal-styled web interfaces with modern web standards. Helpful when you want a dashboard, developer tool, or landing page that looks like a command line. 1,849installs feature The command creates a feature/<name> branch from develop and sets up remote tracking. Use it to start a feature with the Git Flow branch structure. 1,820installs architecture-modernizer Plans service boundaries, event-driven flows, and target architecture for legacy systems. Use it when you need a concrete decomposition plan rather than a code-level refactor. 1,768installs finish Automates Git Flow branch completion by validating tests, merging into target branches, and handling release tagging. 1,712installs monitoring-specialist This subagent helps plan metrics, logs, tracing, alerts, and SLA monitoring. Use it while building observability for an infrastructure project. 1,677installs research-coordinator This subagent turns a broad research brief into specialist assignments and a coordination plan. Use it when a question spans several research disciplines. 1,673installs release Automates Git Flow release branches from develop. It validates semver, bumps package.json, compiles a grouped changelog, and pushes to remote. 1,664installs

Project sponsors

Companies that keep this analytics open

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor