release-changelog

Generate a Paperclip release changelog from commits and changesets.

Updated Mar 28, 2026

Search Tags:#release management #version control #commit analysis #software documentation #changelog generation

Ready to run

npx skills add https://github.com/mhamzahashim/paperclip --skill release-changelog-mhamzahashim

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/mhamzahashim/paperclip/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/mhamzahashim/paperclip --skill release-changelog-mhamzahashim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of release changelogs for Paperclip, extracting information from commits, changesets, and merged pull requests.

Core Features & Use Cases

Automated Changelog Generation: Reads commits and changesets to create a detailed changelog for each stable release.
Versioning Model Understanding: Comprehends Paperclip's calendar versioning system.
User-Friendly Output: Generates a Markdown file with sections for breaking changes, highlights, improvements, fixes, and an upgrade guide.

Quick Start

Use the release-changelog skill to generate the changelog for the next stable release.

Frequently Asked Questions about release-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate changelog generation from commits and merged pull requests?▼

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.

What is calendar versioning and how does it affect release documentation?▼

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.

Can I generate release notes for a specific project using this changelog automation?▼

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.

How to categorize software changes into breaking changes, fixes, and improvements?▼

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.

Does this changelog generator require any external dependencies to run?▼

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.

What is the best way to create an upgrade guide for a new software release?▼

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.