release-changelog

To auto-generate a Paperclip release changelog, this Skill collects commits, changesets, and merged PR context since the last stable tag. It then assembles the data into a user-facing changelog file organized into Breaking Changes, Highlights, Improvements, and Fixes sections.

The changelog file is produced at releases/vYYYY.MDD.P.md, enforcing calver-based versioning rules. This ensures release engineering workflows maintain consistent, time-based version tracking for stable Paperclip releases.

Yes, this Skill is designed for idempotent, CI-friendly workflows to assist release engineers. It reliably gathers git context and PR data to generate a stable changelog without duplicate entries on repeated pipeline runs.

Yes, the generated changelog includes an optional Upgrade Guide when needed. It organizes all changes into Breaking Changes, Highlights, Improvements, and Fixes, providing users with migration context alongside the release notes.

The best way to categorize changesets is to let this Skill automatically parse merged PR context and commit history. It maps the gathered data into structured changelog sections, separating Breaking Changes and Highlights from general Improvements and Fixes.

Gathering context since the last stable git tag ensures the changelog only includes changes relevant to the upcoming release. This Skill uses that boundary to collect commits and PRs, producing an accurate, stable Paperclip release file.