release-changelog

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

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill release-changelog-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/adamtpang/summon.company/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/adamtpang/summon.company --skill release-changelog-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes by hand means digging through git history, changesets, and merged PRs, then formatting everything consistently. This Skill automates that process for Paperclip's calendar-versioned stable releases, producing a ready-to-review changelog file. ## Core Features & Use Cases - Automated changelog generation: Reads commits since the last stable tag, .changeset/*.md files, and merged PRs via gh to build releases/vYYYY.MDD.P.md. - Breaking change detection: Scans migrations, schema diffs, API routes, and BREAKING: commit signals, then writes an upgrade path for each breaking change. - PR and contributor attribution: Adds inline PR links and @-mentions, builds an alphabetized Contributors section, and excludes bots and founders. - Release Case upsert: Optionally syncs the changelog into a Paperclip release Case via the Cases API, with stale-revision retry handling. - Use Case: Before cutting stable release v2026.318.0, run this Skill to produce a categorized changelog with Highlights, Improvements, Fixes, and an Upgrade Guide, ready for maintainer sign-off. ## Quick Start Generate the stable release changelog for the next Paperclip release using commits and merged PRs since the last stable tag.

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 release changelog from git commits?

Run this Skill to collect commits since the last stable tag, changeset files, and merged PRs, then categorize them into Breaking Changes, Highlights, Improvements, and Fixes. The output is written to releases/vYYYY.MDD.P.md for review.

How does calendar versioning work for Paperclip releases?

Paperclip uses calver: stable versions follow YYYY.MDD.P derived from the release date in UTC plus a same-day patch slot. There are no semver major/minor/patch bumps, and canary suffixes never appear in stable changelog filenames.

Can the changelog include PR links and contributor attribution?

Yes. When a bullet maps confidently to a merged PR, the Skill appends the PR link and GitHub usernames inline. A Contributors section lists all authors alphabetically, excluding bots and Paperclip founders, and never exposes email addresses.

What happens if the changelog file already exists?

The Skill performs an idempotency check first. If releases/vYYYY.MDD.P.md exists, it reads and presents the file, then asks whether to keep, regenerate, or update specific sections. It never overwrites silently.

Does this Skill publish the release to GitHub?

No. It only prepares the stable changelog artifact and optionally upserts a release Case via the Paperclip API. Publishing, tagging, and GitHub release creation happen outside this Skill after human sign-off.