Changelog Generator

This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.

Critical Rule: Always Persist to File

ALWAYS write/update the CHANGELOG.md file in the project root. The changelog must be committed alongside the code so it's versioned in git and visible on GitHub.

Workflow

1. Read existing CHANGELOG.md (if it exists) to understand the current format and last documented version
2. Scan git history for commits since the last documented version
3. Generate new entries following the existing format
4. Prepend new entries to CHANGELOG.md (newest version at the top, below the header)
5. Show the user what was added

Never just print the changelog to chat — always write it to the file.

When to Use This Skill