release-changelog

Automatically generate release notes by aggregating git commits, changesets, and merged PR context since the last stable tag. The skill collects these inputs to produce a structured, user-facing changelog without manual entry.

The best way to create a calendar-based stable changelog is to automate the aggregation of commit history and changesets into a compliant markdown file. This ensures consistent formatting like releases/vYYYY.MDD.P.md for product teams.

A changelog generator detects breaking changes by analyzing aggregated commit messages and changeset files since the last stable tag. It categorizes these entries into explicit sections like Breaking Changes, Highlights, Improvements, and Fixes.

Yes, you can use changesets and git tags to assemble release documentation. The skill determines the stable range from the last stable tag and collects changeset data to output a human-readable markdown document with attribution.

Manual release changelog creation is error-prone and time-consuming. Automating the process eliminates manual errors by idempotently gathering commit history and merged PR upgrade notes to produce a consistent document.

An automated stable release changelog includes structured sections for Breaking Changes, Highlights, Improvements, and Fixes. These categories are populated by analyzing commit and PR context for engineering and product teams.