What problem does it solve? Writing release notes from raw commit history is slow and disliked work, and auto-generated notes are just PR titles in merge order. This Skill turns commits, pull requests, and tickets into scannable release notes that answer the reader's real question: does this release cost me work? ## Core Features & Use Cases - Selection and tiering: Reduces messy history to the net diff, drops changes with no consumer surface, and tiers the release by reader impact to decide which surfaces it earns. - Multi-surface output: Produces CHANGELOG.md entries (Keep a Changelog or Common Changelog), git-host release bodies, hosted pages, in-product notes, app-store text, and enterprise advisories, each within its caps and rules. - Verification gate: Ships every delivery with a traceability table mapping entries to commits, an explicit exclusion list, and open items needing a human, with no unsourced performance numbers. - Use Case: Paste a git log range for a v2.4.0 release and receive specification-conformant changelog entries, a release body with summary paragraph, breaking changes in three-part form, and the list of what was deliberately excluded. ## Quick Start Ask the assistant to write the changelog and release notes for your next version from the commits since the previous tag.
