Overview
Git Keep A Changelog is built for releases that deserve a real narrative instead of a commit dump. It reads git history, respects Keep a Changelog structure, and translates a branch or release window into human-readable sections that reflect what changed and why it matters.
The skill is deliberately opinionated about gating. It distinguishes between review mode and yolo / auto mode, enforces release highlights, and asks for explicit confirmation before folding uncommitted work into a concrete changelog draft unless the user explicitly opted into auto-inclusion.
Concepts
- Release storytelling over raw history: commits and diffs are inputs, not the final shape of the changelog.
- SemVer-aware summarization: the release framing is expected to match the kind of change being shipped.
- Worktree safety gates: staged, unstaged, and untracked changes are treated as a decision, not an implicit assumption.
- Highlight-first output: the skill prioritizes the few changes readers need to understand before reading the full entry.
Usage guidance
Use this skill when a repository is approaching release readiness and CHANGELOG.md should be updated with care. It is strongest when you want the agent to draft or revise the entry directly while still preserving structure, scope, and prose quality.
Give it a compare range or release intent if you already know the target. Otherwise let it infer the branch context and work from the current git state. The result should be something a maintainer can review and publish, not just inspect.