release-changelog

Generate a markdown release changelog from repository history since the last stable tag.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Joaoha/xenon-maas --skill release-changelog-joaoha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/Joaoha/xenon-maas/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/Joaoha/xenon-maas --skill release-changelog-joaoha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a user-facing release changelog by aggregating commits, changesets, and merged PR context since the last stable tag, ensuring a consistent, auditable record for XenonMAAS releases.

Core Features & Use Cases

  • Idempotent generation: if a changelog already exists, it will be preserved unless an explicit update is requested.
  • Calver-compliant output: writes a single file at releases/vYYYY.MDD.P.md following the calendar versioning scheme.
  • Comprehensive coverage: includes Breaking Changes, Highlights, Improvements, and Fixes inferred from PRs and commits.
  • Suitable for release workflows: fits in CI/CD pipelines and release planning documents.

Quick Start

Generate the stable releases/vYYYY.MDD.P.md changelog from repository history 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 automatically generate a release changelog from git history and merged PRs?▼

To automatically generate a release changelog from git history, this Skill aggregates commits, changesets, and merged PR context since the last stable tag, producing a categorized markdown file at releases/vYYYY.MDD.P.md.

How does Calver versioning work when generating release files?▼

Calver versioning in this context writes a single output file at releases/vYYYY.MDD.P.md, deriving the calendar version scheme directly from the release date to ensure chronological tracking.

How do I prevent duplicate changelog generation in my CI/CD release workflow?▼

To prevent duplicate changelog generation, the Skill ensures idempotency by checking for an existing output file and preserving it unless an explicit update is requested during the release workflow.

Can I include categorized sections like Breaking Changes and Fixes inferred from commits?▼

Yes, you can include categorized sections like Breaking Changes, Highlights, Improvements, and Fixes inferred directly from your merged PRs and commits to provide comprehensive release coverage.

How do I derive the correct commit range for a stable release changelog?▼

To derive the correct commit range for a stable release changelog, the Skill identifies and calculates the commit history starting from the repository's last stable tag.

Does this changelog generator work for XenonMAAS release planning?▼

Yes, this changelog generator applies specifically to XenonMAAS releases, fitting directly into CI/CD pipelines and release planning documents to ensure an auditable record.