Advanced Changelog Generator Executor

Generate a polished changelog from git history using conventional commit parsing, PR title merging, and customizable formatting templates.

When to Use This Command

Run this command when...

• You are preparing a release and need a changelog generated automatically from commit history
• You want changes grouped by type (features, fixes, breaking changes) without manual sorting
• You need a changelog in a specific format (Keep a Changelog, GitHub Releases, Slack notification)

Avoid this command when...

• You maintain the changelog entirely by hand and do not want it overwritten
• Your commits do not follow any consistent message format

Quick Start

Copy
# .claude/commands/advanced-changelog-generator-executor.md
---
allowed-tools: ["Bash", "Read", "Write"]
---
Parse git log since the last tag. Group commits by type.
Generate a formatted changelog entry. Optionally prepend to
CHANGELOG.md.

Example usage:

/advanced-changelog-generator-executor --since v2.3.0

Example output:

## [2.4.0] - 2026-03-15

### Added
- OAuth2 login with Google and GitHub providers (#142)
- Dashboard analytics chart component (#138)

### Fixed
- Payment webhook timeout handling (#145)
- Mobile navigation menu overlap (#143)

### Changed
- Updated Prisma ORM to v5.8 (#140)
- Optimized CI pipeline caching (#139)

6 entries generated from 32 commits

Core Concepts

Concept	Description
Commit parsing	Extracts type, scope, and description from conventional commit messages
PR linking	Associates commits with pull request numbers and titles
Type grouping	Organizes entries under Added, Fixed, Changed, Breaking Changes sections
Template engine	Formats output using customizable templates for different platforms

git log --since tag --> Parse Commits --> Group by Type
                                              |
                              +-------+-------+-------+
                              |       |       |       |
                           Added   Fixed  Changed  Breaking
                              |       |       |       |
                              +--- Format with Template +
                                         |
                                   Changelog Entry

Configuration

Option	Default	Description
since	last-tag	Starting point for the commit range
format	keepachangelog	Template format (keepachangelog, github, slack)
prepend	true	Prepend the new entry to existing CHANGELOG.md
include-authors	false	Include commit author names alongside entries
breaking-label	BREAKING CHANGES	Section label for breaking changes

Best Practices

1. Use conventional commits -- feat:, fix:, docs: prefixes enable reliable automatic grouping.
2. Tag releases consistently -- the generator uses git tags as boundary markers for commit ranges.
3. Include PR numbers -- merge commits with PR references link changelog entries to detailed context.
4. Review before publishing -- auto-generated changelogs may need minor edits for clarity and audience.
5. Generate at release time -- produce the changelog as part of the release process, not retroactively.

Common Issues

1. Empty changelog generated -- no commits found since the specified tag. Verify that the --since tag value exists in the repo.
2. Duplicate entries -- merge commits and their constituent commits can both appear. Use --no-merges or deduplicate by PR number.
3. Uncategorized commits -- commits without conventional prefixes land in a generic "Other" section. Adopt conventional commits to eliminate this.