What problem does it solve? Writing release notes manually means digging through git history, deciding which commits matter, and formatting entries consistently. This Skill automates that process by reading commits since the last release tag and drafting properly formatted changelog entries. ## Core Features & Use Cases - Automatic Baseline Detection: Finds the most recent git tag with git describe --tags --abbrev=0 when no baseline version is provided. - Commit-to-Changelog Generation: Reviews commits between the baseline and HEAD, filters out insignificant changes (typos, internal refactors), and writes user-facing entries grouped by importance. - Style Preservation: Appends to the existing "Unreleased" section while matching the repository's heading style, bullet format, and ordering conventions. - Use Case: Before cutting a release, run this Skill to populate the Unreleased section of CHANGELOG.md with notable features, fixes, and breaking changes since the last tag, referencing PR numbers where available. ## Quick Start Update the changelog with all notable changes since the last release tag.