Changelog Writing & Auditing

Use this skill when reviewing, drafting, or refining project changelogs. It ensures they follow Keep a Changelog formatting and remain clear to readers.

Core Rules

1. Write for Humans: Changelogs must be clear and readable. They are written for developers and users to understand what changed and why.
2. Do Not Dump Git Logs: Never export git commit messages directly into the changelog. Group and summarize changes into clear, user-facing actions.
3. Chronological Order: Group changes by version release, with the newest version at the top.
4. Link to Releases: Format version headers as links comparing the previous tag with the current tag when possible.

Standard Categories

Group changes under these third-level headers (###):