release-changelog

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

Updated Apr 12, 2026

Search Tags:#automation #git #commits #changesets #pull-requests #calver #release-changelog

Ready to run

npx skills add https://github.com/elijahbowie/ArchonOS --skill release-changelog-elijahbowie

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate the stable Paperclip release changelog by aggregating commits, changesets, and merged PR context since the last stable tag, ensuring consistent, reviewer-friendly release notes.

Core Features & Use Cases

Idempotent generation of releases/vYYYY.MDD.P.md from the latest stable range.
Aggregates commits, changesets, and merged PR context to produce a comprehensive changelog.
Handles Breaking Changes, Highlights, Improvements, and Fixes with an Upgrade Guide when needed.
Supports deterministic file naming and avoids creating canary changelogs.

Quick Start

Generate the stable changelog for the next release in the releases/ directory.

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 release changelogs from git commits and merged pull requests?▼

You can generate a stable release changelog by aggregating commits, changesets, and merged pull request context since the last stable tag. This process automatically compiles git history into a structured, reviewer-friendly release notes file.

What is the file naming format for automated release changelogs using calendar versioning?▼

Automated release changelogs use deterministic file naming with the format releases/vYYYY.MDD.P.md. This ensures idempotent file generation, meaning repeated runs produce consistent results without duplication for calendar versioning releases.

Does automated changelog generation support sectioning for breaking changes and upgrade guides?▼

Yes, automated changelog generation handles proper sectioning including Breaking Changes, Highlights, Improvements, and Fixes. It also generates an Upgrade Guide section automatically when needed to help users navigate release transitions.

Can I use changesets to create a stable release changelog without generating canary versions?▼

Yes, you can aggregate changesets to create a stable release changelog while explicitly avoiding canary changelog creation. The process targets only stable release ranges, pulling context from the latest stable tag forward.

What's the best way to ensure idempotent changelog generation across multiple software release workflows?▼

To ensure idempotent changelog generation across software release workflows, aggregate commits and merged PRs from a stable tag range and write to a deterministic file path. This prevents duplicate entries when re-running the generation process.