What problem does it solve?
Manually maintaining changelogs leads to inconsistent formatting, missed breaking changes, incorrect semantic version bumps, leaked internal commit noise, and non-compliance with the Keep a Changelog 1.1 standard that users and automated tools depend on for release visibility.
Core Features & Use Cases
- Conventional Commits Parsing: Automatically categorizes commit types (feat, fix, breaking change, etc.) into the correct Keep a Changelog 1.1 sections and derives the appropriate semver bump.
- Breaking Change Enforcement: Surfaces all breaking changes with mandatory migration guides to prevent user upgrade failures, and blocks releases if required entries are missing.
- Use Case: For a team preparing a v3.0.0 release, this skill scans commits since the last tag, flags the removed legacy /api/v1 endpoint as a breaking change with a before/after migration snippet, excludes internal chore and CI commits, and drafts a compliant changelog for human review before publishing.
Quick Start
Use the changelog-generator skill to draft a compliant changelog for your next release from your project's recent commit and PR history.