release-changelog

Generate a changelog file from git history, changesets, and PR metadata.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/kangnam7654/stapler --skill release-changelog-kangnam7654
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/kangnam7654/stapler/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/kangnam7654/stapler --skill release-changelog-kangnam7654

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate the user-facing changelog for the stable Paperclip release by reading commits, changesets, and merged PR context since the last stable tag.

Core Features & Use Cases

  • Idempotent output: writes to releases/vYYYY.MDD.P.md and preserves a stable artifact across runs unless a new release is prepared.
  • Data aggregation: collects git history, changesets, and merged PR context to compose sections such as Breaking Changes, Highlights, Improvements, and Fixes.
  • Release workflow support: suitable for CI/CD pipelines or manual release processes to deliver publish-ready notes.

Quick Start

Run the release-changelog skill to generate the changelog for the current 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 automatically generate release notes from git history and merged pull requests?

Automatically generate release notes by reading git history, changesets, and merged PR metadata to summarize release notes. This process collects commit data and PR context to compose categorized, publish-ready notes for your stable release.

What is the best way to categorize breaking changes and improvements in a project changelog?

Categorize breaking changes and improvements by aggregating changesets and merged PR context into distinct changelog sections. This approach separates Breaking Changes, Highlights, Improvements, and Fixes into clearly defined parts within the release notes file.

How do I create idempotent release notes for CI/CD pipelines?

Create idempotent release notes by writing output to a versioned file like releases/vYYYY.MDD.P.md. This preserves a stable artifact across pipeline runs unless a new release is prepared, ensuring consistent delivery in automated workflows.

Does generating a changelog from changesets require a specific versioning scheme?

Generating a changelog from changesets applies to projects using a Calver-style versioning scheme with a latest stable tag. It reads commits and changesets since the last stable tag to output the release file.

Can I use changesets and PR metadata to summarize release notes for manual release processes?

Yes, you can use changesets and PR metadata to summarize release notes for manual release processes. The workflow reads git history and PR context to deliver publish-ready notes suitable for either CI/CD pipelines or manual execution.