skills.rest
Jang-zn
Jang-znCOMMUNITY
Explore all skills by this author →
GitHub

release-changelog

Generate release changelogs from commits, changesets, and PRs into releases/vYYYY.MDD.P.md.

Updated Apr 3, 2026
Search Tags:#automation#git#changelog#documentation#attribution#release-notes#calver
One-click install
npx skills add https://github.com/Jang-zn/paperclip-kr --skill release-changelog-jang-zn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/Jang-zn/paperclip-kr/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/Jang-zn/paperclip-kr --skill release-changelog-jang-zn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generates a user-facing release changelog for stable Paperclip releases by aggregating commits, changesets, and merged PR context since the last stable tag.

Core Features & Use Cases

  • Automated changelog assembly: Aggregates git commits, changesets, and PR context into a single release narrative.
  • Calver-aware outputs: Produces a file at releases/vYYYY.MDD.P.md aligned with calendar versioning.
  • Upgrade and attribution: Includes breaking changes and PR attributions to simplify upgrades and reviewer actions.

Quick Start

Run this skill to generate the stable release changelog file at releases/vYYYY.MDD.P.md using the latest tag context.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I automate release notes generation from git commit history?▼

Automating release notes generation from git commits involves aggregating commit messages, changesets, and merged pull request context since the last stable tag to assemble a single user-facing release narrative.

How does calver-based tagging work for generating changelog files?▼

Calver-based tagging for changelog files uses calendar versioning to produce output paths like releases/vYYYY.MDD.P.md, ensuring release notes align chronologically with the tagged release date.

How do I group breaking changes and improvements into structured release notes?▼

Grouping breaking changes and improvements into structured release notes requires detecting breaking changes from sources and categorizing aggregated items into distinct sections like Highlights, Improvements, Fixes, and Upgrade Guide.

Can I generate contributor attributions automatically from merged pull requests?▼

Generating contributor attributions automatically from merged pull requests is supported by aggregating PR context and formatting contributor attributions directly into the final release changelog file.

Does idempotent writing work when regenerating stable release changelogs?▼

Idempotent writing works when regenerating stable release changelogs, allowing the release workflow to safely overwrite the releases/vYYYY.MDD.P.md file without duplicating aggregated commit entries.

What is the best way to detect breaking changes for an upgrade guide in release notes?▼

The best way to detect breaking changes for an upgrade guide in release notes is to read source changesets and commit history, isolating breaking modifications to format them into a dedicated Upgrade Guide section.

Related Skills

Explore More Software Engineering Skills→
DimillianDimillian
3.9k

app-store-changelog

Generates App Store release notes from git history since last tag.

Community
Basic
navyapdh11navyapdh11

release-changelog

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

Community
Intermediate
pth-droidpth-droid

release

Automate changelog creation, version bumping, and release pull requests.

Community
Advanced
Tai-ch0802Tai-ch0802
41

release-notes

Generate bilingual markdown release notes for GitHub releases.

Community
Intermediate