What problem does it solve? Writing release notes by hand means reading through dozens or hundreds of commits and translating developer jargon into user-facing language. This Skill automates that process by analyzing git history, categorizing commits, and producing a polished changelog. ## Core Features & Use Cases - Flexible Commit Ranges: Generate changelogs between tags, since the last release, over date ranges, or between arbitrary refs. - Smart Categorization: Maps commits to Keep a Changelog categories (Added, Changed, Fixed, Security, Deprecated, Removed, Infrastructure) using conventional commit prefixes and content signals. - User-Facing Rewrites: Transforms internal commit messages like "refactor: extract useAuth hook" into meaningful entries like "Improved authentication flow reliability". - Multiple Output Formats: Produces Keep a Changelog Markdown, GitHub Release notes, or concise Slack summaries. - Use Case: Before shipping v1.2.0, ask for a changelog since v1.1.0 and receive a categorized, deduplicated release summary with PR references and a compare link. ## Quick Start Ask the assistant to generate a changelog of all commits since the last tag in this repository.