release-changelog

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

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/Lautaro073/zCorvus_agents --skill release-changelog-lautaro073
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/Lautaro073/zCorvus_agents/tree/main/AI_Workspace/Agents/Frontend/skills/release-changelog
Command: npx skills add https://github.com/Lautaro073/zCorvus_agents --skill release-changelog-lautaro073

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate a user-facing changelog for Paperclip stable releases by aggregating commits, changesets, and merged PR context since the last stable tag.

Core Features & Use Cases

  • Reads git history since the last stable tag and merges it with changeset data to surface user-facing notes.
  • Produces a structured changelog with sections for Breaking Changes, Highlights, Improvements, and Fixes, ready for publication.
  • Idempotent: respects existing releases/vYYYY.MDD.P.md files and avoids unintended overwrites.
  • Use Case: Maintainers generate release notes for a scheduled stable release to inform users and contributors.

Quick Start

Run the skill to generate the latest stable changelog from commits 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 auto-generate a changelog from git commits and changesets?

To auto-generate a changelog, aggregate recent git logs, .changeset files, and merged PR details since the last stable tag. This compiles user-facing release notes into structured sections for Breaking Changes, Highlights, Improvements, and Fixes.

How do I generate release notes from git history and changesets?

Generate release notes by reading git history since the last stable tag and merging it with changeset data. This surfaces user-facing notes and outputs a structured changelog file ready for publication.

Can I prevent a changelog generator from overwriting an existing release file?

Yes, you can preserve idempotency and avoid overwriting existing files. The tool respects existing releases/vYYYY.MDD.P.md files, ensuring it avoids unintended overwrites when generating stable changelogs.

Does the changelog generation process include merged PR details?

Yes, merged PR details are included in the changelog generation. The tool locates the last stable tag and combines git logs, .changeset files, and merged PR context to populate the release notes sections.

What is the best way to structure release notes for breaking changes and fixes?

The best way to structure release notes is to categorize aggregated git commits and changesets into specific sections. The tool automatically populates sections for Breaking Changes, Highlights, Improvements, and Fixes into a markdown file.

Will this tool generate canary changelogs alongside the stable release?

No, the tool only generates the stable release changelog file releases/vYYYY.MDD.P.md. It explicitly avoids creating canary changelogs, focusing solely on aggregating context since the last stable tag.