skills.rest
travelinman1013
travelinman1013COMMUNITY
Explore all skills by this author →
GitHub

release-changelog

Generate a publish-ready changelog at releases/vYYYY.MDD.P.md from commits, changesets, and merged PRs.

Updated Apr 16, 2026
Search Tags:#automation#git#changelog#release#changeset#pr-context#calver
One-click install
npx skills add https://github.com/travelinman1013/royclip --skill release-changelog-travelinman1013
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/travelinman1013/royclip/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/travelinman1013/royclip --skill release-changelog-travelinman1013

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a stable release changelog by aggregating commits, changesets, and merged PR context since the last stable tag for Paperclip releases.

Core Features & Use Cases

  • Aggregates commits since the last stable tag.
  • Incorporates changesets and merged PR context to produce a reliable changelog file.
  • Outputs the changelog to releases/vYYYY.MDD.P.md, ready for publication on release day.

Quick Start

Run the skill to generate the next stable release changelog at releases/vYYYY.MDD.P.md.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I auto-generate a changelog for calver stable releases?▼

To auto-generate a changelog for calver stable releases, the skill aggregates commits, changesets, and merged PR context since the last stable tag. It outputs a publish-ready markdown file at releases/vYYYY.MDD.P.md.

What is the best way to generate release notes from git commits and changesets?▼

Generating release notes from git commits and changesets involves reading all commits since the last stable tag and incorporating merged PR context. This approach produces a reliable, user-facing changelog file ready for publication.

How do I aggregate merged PR context into a publish-ready changelog?▼

Aggregating merged PR context into a publish-ready changelog requires collecting pull request details alongside commits and changesets since the last stable tag. The final markdown is generated at releases/vYYYY.MDD.P.md.

Do I need a specific git tag format to generate a calver changelog?▼

Generating a calver changelog requires a previous stable git tag to calculate the diff. The skill reads commits since the last stable tag and outputs the file using the vYYYY.MDD.P.md naming convention.

Can I use this changelog automation without changesets in my repository?▼

Changelog automation without changesets relies entirely on aggregating commits and merged PR context. While changesets enhance the output, the skill reads all available git history since the last stable tag to produce the markdown.

Related Skills

Explore More Software Engineering Skills→
gancimgancim

release-changelog

Generate a stable release changelog from commits, changesets, and PR metadata.

Community
Advanced
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
michaelsvanbeekmichaelsvanbeek
1

git-workflow

Codify Git commit, branch, and PR practices with Conventional Commits.

Community
Advanced
Doyajin174Doyajin174
1

changelog-generator

Convert git commit history into categorized Markdown release notes.

Community
Intermediate