release-changelog

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

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/lucasadcapital-beep/ancora-auto --skill release-changelog-lucasadcapital-beep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/lucasadcapital-beep/ancora-auto/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/lucasadcapital-beep/ancora-auto --skill release-changelog-lucasadcapital-beep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

Core Features & Use Cases

  • Idempotent changelog generation that updates only the target file if needed.
  • Aggregates commits, changesets, and merged PR context to produce accurate release notes.
  • Useful for release engineering, stakeholder communication, and documented release plans.

Quick Start

Run the release-changelog skill to generate the changelog for the latest stable Paperclip release.

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 changelog generation from git commits and merged PRs?

Automate release changelog generation by aggregating git commits, changesets, and merged PR context into structured release notes. The skill reads repository history since the last stable tag to draft accurate changelogs automatically.

What is the best way to structure breaking changes and highlights in a release changelog?

Structure release changelogs by enforcing standardized sections for Breaking Changes, Highlights, Improvements, and Fixes. This categorization organizes aggregated commits and changesets into clear, stakeholder-ready release documentation.

How do I generate CalVer release notes in a single markdown file?

Generate CalVer release notes by producing a single versioned markdown file named releases/vYYYY.MDD.P.md. The skill applies CalVer versioning rules to create structured, file-based release documentation.

Can I use an idempotent changelog generator for repeated release engineering workflows?

Use an idempotent changelog generator to safely run repeated release engineering workflows without duplicating content. The skill updates only the target releases/vYYYY.MDD.P.md file if changes are actually needed.

Does automated changelog drafting support stakeholder communication for software releases?

Automated changelog drafting supports stakeholder communication by translating raw repository changes into structured release notes. It aggregates development history into clear highlights and fixes for documented release plans.