release-changelog

Name: release-changelog
Availability: InStock
Author: Bini

Generate stable release changelogs from git commits, changesets, and merged PRs.

14|2|Updated Mar 6, 2026

Search Tags:#automation #git #changelog #developer tools #documentation #release notes

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of user-facing changelogs for stable software releases, ensuring consistency and saving developers significant time.

Core Features & Use Cases

Automated Changelog Generation: Reads commits, changesets, and PR data to compile a changelog.
Breaking Change Detection: Identifies and flags breaking changes for user awareness.
Categorization: Organizes changes into standard sections like 'Breaking Changes', 'Highlights', 'Improvements', and 'Fixes'.
Use Case: Before releasing a new version of Paperclip, this skill can be invoked to draft the releases/vX.Y.Z.md file, summarizing all user-impacting changes since the last stable release.

Quick Start

Generate the stable Paperclip release changelog for the next version.

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 git commits and merged PRs?▼

Automate changelog generation by analyzing git commits, changesets, and merged PRs to compile user-facing release notes. The process categorizes updates into standard sections like Improvements and Fixes, ensuring consistency and saving developers significant time.

How does breaking change detection work when generating release notes?▼

Breaking change detection for release notes works by analyzing git commits and merged PR data to identify and flag changes that break existing functionality. It then categorizes these updates into a dedicated section for user awareness and clarity.

What is the best way to organize release notes into predefined categories?▼

Organize release notes into predefined categories by analyzing git commits and changesets to group updates into standard sections like Breaking Changes, Highlights, Improvements, and Fixes, ensuring user clarity and consistent documentation.

Can I generate a stable release changelog without overwriting an existing file?▼

Yes, you can generate a stable release changelog without overwriting an existing file. The process ensures idempotency by checking for existing changelog files before generation, preventing duplicate or overwritten release documentation.

How do I draft a release markdown file summarizing all changes since the last stable release?▼

Draft a release markdown file by analyzing git commits, changesets, and merged PRs since the last stable release. This summarizes all user-impacting changes and categorizes them into sections like Highlights and Fixes for the new version.

Do I need changesets to generate user-facing release documentation?▼

You do not strictly need changesets to generate user-facing release documentation, as the process can analyze git commits and merged PRs. However, incorporating changesets alongside commit data provides a more comprehensive summary of user-impacting changes.