release-changelog

This Skill aggregates commits, changesets, and merged PR context since the last stable tag to build a complete release changelog. It automatically categorizes updates into sections like Highlights, Improvements, and Fixes.

Calver versioning applies to release notes by outputting the changelog file at releases/vYYYY.MDD.P.md. This convention ensures stable releases are chronologically organized, while canary tags are explicitly excluded from generating changelogs.

You document breaking changes and upgrade guidance by enforcing a defined section structure within the aggregated changelog. When breaking changes are detected from PRs or changesets, the output includes dedicated upgrade instructions for users.

Yes, you can exclude canary releases from the automated changelog output. The generation workflow is designed specifically for stable releases and inherently skips canary tags to prevent unstable changes from appearing in user-facing notes.

Yes, the changelog generation process enforces idempotency for repeated runs. This ensures that executing the aggregation workflow multiple times against the same stable tag produces identical changelog output without duplicating entries.