release-changelog

Automated changelog generation reads commits, changesets, and merged pull requests since the last stable tag to produce a categorized Markdown file. It extracts breaking changes, highlights, improvements, and fixes directly from your repository history without manual entry.

Calendar versioning uses date-based release tags rather than semantic version numbers. This Skill comprehends calendar versioning schemes to correctly identify the last stable tag and generate accurate release changelogs based on chronological project milestones.

This Skill is specifically designed to generate stable Paperclip release changelogs. It reads project-specific commits and changesets to create a user-facing Markdown file with sections for breaking changes, highlights, improvements, fixes, and an upgrade guide.

Categorizing software changes is handled automatically by analyzing commit messages and changeset context since the last stable release. The generated Markdown output organizes entries into distinct sections for breaking changes, highlights, improvements, fixes, and an upgrade guide.

No external dependencies are required to run this changelog generator. The Skill operates independently using internal scripts to read repository context and generate the final Markdown documentation without needing additional software packages.

Creating an upgrade guide is integrated directly into the changelog generation process. By reading merged PR context and changesets, the Skill produces a Markdown file that includes a dedicated upgrade guide section alongside categorized release notes.