shine-changelog-draft

You can generate a changelog from git commits by running this skill on your repository. It reads git log history, categorizes commits into standard Keep-a-Changelog sections, and produces a ready-to-paste entry for your CHANGELOG.md file.

The Keep-a-Changelog format structures release notes into Added, Changed, Deprecated, Removed, Fixed, and Security categories. This skill automatically sorts your git commits into these exact sections, appending a versioned and dated entry to your changelog.

Yes, you can automate SemVer versioning in release notes with this skill. It respects Semantic Versioning conventions, automatically flags breaking changes found in commit history, and generates a versioned changelog entry with the current date.

To categorize git commits into Added, Changed, Fixed, and Security sections, this skill analyzes your repository history using git log. It automatically classifies each commit into the appropriate Keep-a-Changelog category for your release notes.

Yes, this changelog generator works without external dependencies or components. It operates directly on your repository history using standard git log commands to extract and categorize commits into a Keep-a-Changelog formatted entry.

You should use an automated changelog drafter when you want to save time during releases and ensure consistent release notes. It sources all facts directly from repository history, preventing missed updates and maintaining formatting consistency across versions.