skills.rest
gancim
gancimCOMMUNITY
Explore all skills by this author →
Website𝕏@MrGanciGitHub

release-changelog

Generate a stable release changelog from commits, changesets, and PR metadata.

Updated Mar 25, 2026
Search Tags:#automation#git#changelog#release#changesets#pull-requests#calver
One-click install
npx skills add https://github.com/gancim/sprint --skill release-changelog-gancim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/gancim/sprint/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/gancim/sprint --skill release-changelog-gancim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The manual process of compiling release notes from scattered commits, changesets, and merged PR context is time-consuming and error-prone. This skill automates the creation of a single, user-facing changelog document for each stable Sprint release.

Core Features & Use Cases

  • Aggregates commits, changesets, and merged PR context to compose a complete release changelog.
  • Produces the canonical file at releases/vYYYY.MDD.P.md and is idempotent across runs.
  • Supports the CalVer-based release model and can be integrated into CI/CD workflows to generate release notes automatically.

Quick Start

Use the release-changelog skill to generate the stable release notes for the upcoming sprint by triggering it in your CI pipeline.

Frequently Asked Questions about release-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release changelogs from git commits and pull requests automatically?▼

Generating release changelogs automatically involves aggregating git commits, changesets, and merged pull request context into a structured document. This creates a user-facing file with highlights, improvements, fixes, and upgrade notes.

What is the best way to compile changesets and merged PR context into release notes for CI/CD?▼

To compile changesets and merged PR context into release notes for CI/CD, aggregate git history and pull request metadata since the last stable tag. This produces a structured changelog file for pipeline integration.

Does automated changelog generation work with CalVer-based release workflows?▼

Automated changelog generation fully supports CalVer-based release workflows by aggregating git history since the last stable tag. It outputs the structured document directly to a CalVer-formatted file path like releases/vYYYY.MDD.P.md.

How do I create a structured release document with highlights and fixes from recent commits?▼

You create a structured release document with highlights and fixes by aggregating commits, changesets, and merged pull request context. This categorizes the changes into highlights, improvements, fixes, and upgrade notes for users.

What are the limitations of using commit history to generate stable release notes?▼

The limitation of using commit history to generate stable release notes is its reliance on accurate changesets and PR metadata. The process is idempotent across runs but requires a valid previous stable tag to aggregate changes correctly.

Related Skills

Explore More Software Engineering Skills→
Tigha66Tigha66

release-changelog

Generates a Markdown changelog from git history, categorizing changes by type for each release.

Community
Advanced
mkrlabsmkrlabs

github-release

Automate GitHub releases with tag validation and build checks.

Official
Advanced
kengerlwlkengerlwl
82

release

Automate git tag creation, pushing, and CI/CD trigger initiation.

Community
Intermediate
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate