release-changelog

Name: release-changelog
Availability: InStock
Author: tigha66

Generates a Markdown changelog from git history, categorizing changes by type for each release.

Updated Mar 14, 2026

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

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and 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 time.

Core Features & Use Cases

Automated Changelog Generation: Reads commits, changesets, and PR data to compile a changelog.
Breaking Change Detection: Identifies and categorizes breaking changes for clear user communication.
Use Case: Before releasing a new version of Paperclip, use this Skill to generate the releases/vX.Y.Z.md file, summarizing all significant changes since the last stable release.

Quick Start

Generate the stable changelog for the next release.

Frequently Asked Questions about release-changelog

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

FAQPage Schema

How do I generate a changelog from git commits and merged pull requests?▼

To generate a changelog from git commits, this Skill analyzes changesets and merged pull request context since the last stable tag. It automatically categorizes changes into Breaking Changes, Highlights, Improvements, and Fixes for user-facing clarity.

What is the best way to automate release notes for a new software version?▼

Automating release notes is handled by analyzing git history and PR data to compile a structured changelog file. This ensures consistency across releases and saves developers time by eliminating manual documentation efforts.

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

Breaking change detection works by scanning git commits and changesets to identify modifications that impact existing functionality. The Skill then categorizes these changes separately in the changelog to ensure clear user communication.

Can I use this changelog generator for any git repository or does it require specific changesets?▼

This changelog generator analyzes git commits, changesets, and merged pull request context since the last stable tag. It is designed to generate stable release changelogs, ensuring adherence to release standards for user-facing clarity.

How do I categorize improvements and fixes in my automated changelog?▼

To categorize improvements and fixes in an automated changelog, the Skill reads commit history and PR context to sort changes into distinct sections. It groups updates into Breaking Changes, Highlights, Improvements, and Fixes.

Why should I automate changelog generation instead of manually writing release documentation?▼

Automating changelog generation ensures consistency and saves developers time by eliminating manual documentation efforts. It compiles git commits and PR data into a structured file, ensuring user-facing clarity and adherence to release standards.