Changelog Generator

Purpose: Transform raw git commit history into a human-readable, user-facing CHANGELOG entry in Keep a Changelog format. Categorizes commits, rewrites them in plain language, and recommends the correct semver version bump.

Invocation

/changelog [since-tag]

Internally runs:

git log $(git describe --tags --abbrev=0)..HEAD --format="%H %s" --no-merges

If since-tag is provided, uses that as the baseline instead of auto-detecting the last tag.

Process

Step 1: Collect Commits

git log [since-tag]..HEAD --format="%H|||%s|||%b" --no-merges

If no commits found: output "No changes since last release."

Step 2: Categorize by Conventional Commit Prefix

Non-conventional commits: use judgment based on commit message content.

Step 3: Rewrite for Humans

Transform commit messages into user-facing language:

• fix(auth): resolve JWT expiry edge case → "Fixed a login session expiry bug that logged users out unexpectedly"
• feat(dashboard): add export button → "Added CSV export to the analytics dashboard"
• Group related commits into a single entry if they're part of the same feature

Step 4: Recommend Version Bump

Output Format

## [VERSION] — YYYY-MM-DD

### Breaking Changes
> ⚠️ Migration required: [what users need to change]
- [Breaking change with migration guide]

### Added
- [New feature in plain language] (#PR or commit hash)

### Fixed
- [Bug fixed and user impact explained]

### Changed
- [Improvement with context]

### Removed
- [What was removed and what to use instead]

### Security
- [Vulnerability addressed — always list, never omit]

Rules

• Security section must always be listed if any security commit exists — never bury it
• Breaking changes section comes first, always
• Omit chore:, test:, ci: commits — they are not user-facing
• Every entry should explain user impact, not just code change
• If a breaking change has no migration guide: write "Migration guide: [TODO]" — don't omit the section
• Suggest the version number explicitly in the output header