release-changelog

Generate a stable release changelog Markdown file from commits, changesets, and merged PRs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kysonttan-sys/1percent-AI-Labs --skill release-changelog-kysonttan-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/kysonttan-sys/1percent-AI-Labs/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/kysonttan-sys/1percent-AI-Labs --skill release-changelog-kysonttan-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a stable release changelog file (releases/v{version}.md) by aggregating commits, changesets, and merged PRs since the last stable tag, ensuring consistent documentation across releases.

Core Features & Use Cases

  • Idempotent generation: re-run without duplicating content
  • Last stable tag detection: identifies v{last-stable} accurately
  • Input aggregation: collects git commits, changesets, and merged PR context
  • User-facing output: produces a structured releases/v{version}.md with sections like Breaking Changes, Highlights, Improvements, and Fixes
  • Canary handling: preserves the canonical filename releases/v1.2.3.md even if canary versions exist
  • Upgrade guidance: includes an upgrade path for breaking changes when needed

Quick Start

Invoke the release-changelog skill to generate releases/v{version}.md for the upcoming 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 auto-generate stable release changelogs from git commits and merged PRs?

To auto-generate a stable release changelog, the skill aggregates git commits, changesets, and merged PRs since the last stable tag, categorizing them into structured Markdown sections like Breaking Changes and Fixes.

What is the best way to generate release notes while handling canary version suffixes?

Generating release notes with canary suffixes requires preserving the canonical filename format releases/v{version}.md. The skill detects the last stable tag and outputs a predictable Markdown file regardless of canary versions.

How does changelog generation detect the last stable tag in a release workflow?

Changelog generation detects the last stable tag by scanning the git history to identify the most recent stable version marker, then collects all commits and changesets submitted after that tag to compile the release notes.

Can I re-run changelog generation without duplicating content in the Markdown file?

Yes, the changelog generation process is idempotent, meaning you can re-run it multiple times without duplicating content. It safely aggregates commits and changesets into the releases/v{version}.md file.

How do I include upgrade guidance for breaking changes in auto-generated release notes?

To include upgrade guidance for breaking changes, the skill identifies breaking changes during commit aggregation and automatically appends an upgrade path section within the structured releases/v{version}.md Markdown output.

Does automated changelog generation work with changesets for versioning?

Yes, automated changelog generation works with changesets by collecting them as primary inputs alongside git commits and merged PRs to produce a comprehensive user-facing Markdown file for the release.