release-changelog

Aggregate commits, changesets, and merged PRs into a stable release changelog.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Mothership-Foundry/foundry-dashboard --skill release-changelog-mothership-foundry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/Mothership-Foundry/foundry-dashboard/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/Mothership-Foundry/foundry-dashboard --skill release-changelog-mothership-foundry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Release Changelog Skill automates the creation of the user-facing changelog for Paperclip releases by aggregating commits, changesets, and merged PR context since the last stable tag, ensuring a consistent and complete release note.

Core Features & Use Cases

  • Idempotent changelog generation that safely recreates the release note without duplicating content.
  • Aggregates inputs from git commits, changesets, and merged PRs to produce a comprehensive, user-facing document.
  • Detects breaking changes and includes upgrade guidance, with proper attribution when PR data is available.
  • Produces a standardized template file at releases/vYYYY.MDD.P.md that can be published to release channels.

Quick Start

Generate the stable release changelog by running the skill against the repository to create the file 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 release changelogs from git commits and merged pull requests?

To auto-generate release changelogs, aggregate git commits, changesets, and merged PR context since the last stable tag. This process detects breaking changes, categorizes user-facing updates, and applies structured templates to produce a standardized release note.

How does idempotent changelog generation work for calendar-versioned releases?

Idempotent changelog generation safely recreates the release note without duplicating content. It applies to calendar-versioned (CalVer) release workflows by reprocessing the same commit and PR context to consistently output the identical changelog file.

What's the best way to detect breaking changes and include upgrade guidance in release notes?

The best way to detect breaking changes is to aggregate merged pull request context and changesets. This automatically identifies breaking updates, includes upgrade guidance, and ensures proper attribution when PR data is available.

Can I generate a standardized changelog template file for my release workflow?

Yes, you can generate a standardized changelog template file. The output is created at releases/vYYYY.MDD.P.md, which captures user-facing categorizations, breaking changes, and aggregated commits ready for release channel publication.

Does this changelog automation work with calendar versioning?

Yes, this changelog automation explicitly handles calendar-versioned (CalVer) release workflows. It evaluates git history and merged PR context since the last stable tag to populate the CalVer-formatted release template.

Why are my auto-generated release notes missing context from recent changesets?

Auto-generated release notes may miss context if changesets are not properly aggregated with git commits and merged PRs since the last stable tag. Comprehensive input gathering across all three sources ensures complete user-facing documentation.