changelog-writer

To generate a changelog from conventional commits, this Skill analyzes your git history and automates classification, formatting, breaking change detection, and version bump recommendations. It outputs Keep a Changelog formatted entries directly from your commit messages.

Yes, you can automatically detect breaking changes and suggest semantic version bumps. This Skill analyzes commit history to identify backward-incompatible changes and recommends major, minor, or patch version bumps based on conventional commit types.

The best way to draft release notes and migration guides from git history is using this Skill to summarize key changes and generate step-by-step instructions. It automates user-facing release notes drafting directly from conventional commits.

Yes, this changelog generator requires conventional commits format to parse git history accurately. It relies on structured commit messages to classify changes, detect breaking changes, and format Keep a Changelog output correctly.

To create migration guides, this Skill processes git history to identify breaking changes and generates step-by-step instructions. It assists in drafting user-facing migration guides ensuring smooth transitions between software versions.

Release note generation operates via command-line scripts for commit classification and changelog formatting. Limitations include dependency on conventional commit formats and requiring git history access to automate Keep a Changelog output and version bump recommendations.