Changelog Generator
Generates a human-readable changelog between two git tags — grouped by feat, fix and refactor, with author attribution.
Entry verified April 21, 2026
The short answer
Changelogs are tedious but high-value. This skill reads the conventional-commit history between two refs and produces a clean CHANGELOG.md entry in Keep-a-Changelog format, so you start a release with a proper Added / Changed / Fixed draft instead of a blank file.
When to use it
Every release. Before drafting release notes for a public repo, where a neat changelog is often what the reader sees before the code.
Setup
- 1
Save the file as ~/.claude/commands/changelog.md.
- 2
Works best on repos that already follow conventional commits — the feat/fix/refactor prefixes drive the grouping.
- 3
Invoke with two refs, e.g. /changelog v1.2.0 v1.3.0 or /changelog v1.2.0 HEAD.
- 4
Output is a ready-to-paste Keep-a-Changelog block — review once, then drop into CHANGELOG.md.
Example
You: /changelog v1.2.0 HEAD Claude: [produces Keep-a-Changelog section with Added / Changed / Fixed blocks, 23 commits grouped]
Source & attribution
- Author
- Bryan Collins
- Licence
- MIT
- Type
- Original
Original pattern published under MIT — attribution preserved by convention, not licence requirement.
Caveats
Only as good as your commit messages. 'wip' commits break the grouping.
56 skills across 10 categories, all licence-verified.