release-changelog

To generate a changelog from commit history automatically, this Skill analyzes commits and changesets made since the last stable tag. It applies calendar versioning rules to categorize breaking changes, highlights, improvements, and fixes into a structured markdown file.

Calendar versioning for release changelogs organizes version numbers using the vYYYY.MDD.P format based on the release date. This Skill applies these rules when generating the markdown file, ensuring the changelog structure aligns with the specific Paperclip release timeline.

After marking a version as stable, you create a release changelog by running this Skill to analyze the commit history. It processes the changesets and outputs the generated changelog directly to a file named releases/vYYYY.MDD.P.md for user review.

The best way to categorize breaking changes and improvements in a changelog is through automated commit and changeset analysis. This Skill parses the commit history to separate updates into distinct categories like breaking changes, highlights, improvements, and fixes.

Yes, you can use commit analysis to track updates for Paperclip releases. This Skill reads the commit history and changesets since the last stable tag to automatically identify and document all relevant changes, saving time and reducing human error.

A limitation when generating changelogs from changesets is that the output is specifically tailored for Paperclip releases using calendar versioning. It generates a markdown file for user review rather than publishing the changelog directly to a platform automatically.