What problem does it solve? Writing changelogs and release notes manually from raw git history is tedious and error-prone, often resulting in inconsistent formatting, missed breaking changes, and incorrect version bumps. ## Core Features & Use Cases - Commit Analysis & Categorization: Parses conventional commits, PR titles, and issue references, grouping changes into Added, Fixed, Changed, Breaking Changes, and other Keep a Changelog sections. - Semantic Versioning Suggestions: Detects breaking changes via BREAKING CHANGE footers and ! markers, then recommends the correct MAJOR, MINOR, or PATCH version bump. - Dual Output Formats: Produces both a developer-facing CHANGELOG.md and user-friendly release notes with highlights, contributors, and installation instructions. - Use Case: Before tagging v2.1.0, run this Skill against commits since the last release to generate a formatted changelog, draft GitHub release notes, and a migration guide for any breaking API changes. ## Quick Start Generate a changelog and release notes from all commits since the last git tag and suggest the next semantic version.