release-changelog

You can generate a changelog from git commits automatically by invoking this Skill to read your commit history, changesets, and merged PRs since the last stable tag. It then categorizes updates and flags breaking changes for user clarity.

Detecting breaking changes for release notes is handled by analyzing merged PRs and commit data. The Skill identifies critical updates that require user attention and categorizes them into a dedicated 'Breaking Changes' section in the final changelog.

The best way to categorize updates in a software changelog is to analyze commit data and organize changes into predefined, user-friendly sections. This Skill automatically sorts updates into 'Breaking Changes', 'Improvements', and 'Fixes' for maximum user clarity.

Yes, you can include contributor attribution when generating release notes. This Skill automatically extracts contributor information from merged PRs and formats it inline within the generated changelog document.

You do not strictly need changesets to create an automated changelog, as the Skill can analyze git commits and merged PRs independently. However, incorporating changesets alongside commit data provides a more comprehensive and accurate release log.

A limitation of using git commits for changelog generation is that the output relies entirely on commit message and PR data quality. If commit messages lack clear context or breaking change indicators, the automated categorization may miss critical updates.