skills.rest
rishith-c
rishith-cCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-changelog

Your independent AI + message from the one,<br> who sent it. No, wait, wrong one:)

2|Updated Mar 29, 2026
Search Tags:#automation#git#changelog#release#pull-request#calver
One-click install
npx skills add https://github.com/rishith-c/staple --skill release-changelog-rishith-c
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/rishith-c/staple/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/rishith-c/staple --skill release-changelog-rishith-c

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate the user-facing changelog for the stable Staple release by aggregating commits, changesets, and merged PR context since the last stable tag.

Core Features & Use Cases

  • Automates stable release notes generation using calendar-based versioning (calver).
  • Reads commits, changesets, and merged PR context to produce a structured release document.
  • Writes to releases/vYYYY.MDD.P.md and enforces idempotent updates with proper sections (Breaking Changes, Highlights, Improvements, Fixes).

Quick Start

Run the release-changelog skill to generate the file releases/vYYYY.MDD.P.md from the latest commits and PR context.

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 release notes from git commits and merged pull requests?▼

Automatically generate release notes by collecting commits, changesets, and merged PR context since your last stable tag. The output is a structured markdown file written to releases/vYYYY.MDD.P.md with sections for Breaking Changes, Highlights, Improvements, and Fixes.

What is calendar-based versioning (calver) and how does it structure stable release files?▼

Calendar-based versioning (calver) structures stable release files using the vYYYY.MDD.P naming convention. It enforces this version format on the generated changelog file, ensuring chronological tracking and idempotent updates to the release notes document.

How do I prevent duplicate entries when generating a changelog for consecutive stable releases?▼

Prevent duplicate changelog entries by enforcing idempotency checks during the generation process. The system verifies the existing releases/vYYYY.MDD.P.md file and applies structured updates, ensuring repeated runs do not overwrite or duplicate aggregated commit and PR context.

Can I categorize breaking changes and highlights separately when aggregating changesets?▼

Categorize breaking changes and highlights separately by enforcing a structured release-notes layout. The generated changelog aggregates changesets and PR context into distinct sections, specifically separating Breaking Changes, Highlights, Improvements, and Fixes for clear user-facing documentation.

What is the best way to compile user-facing release notes for a stable release without manual formatting?▼

Compile user-facing release notes automatically by aggregating git commits and merged PR context into a predefined markdown layout. This approach enforces calendar-based versioning and idempotent updates, eliminating manual formatting by directly writing the structured output file.

Related Skills

Explore More Software Engineering Skills→
tamzitamzi

release-changelog

Generates stable Paperclip changelogs from Git commit history, GitHub pull requests, and Calab for versioning/release tracking.

Community
Advanced
MaxSaietsMaxSaiets

openclaw-release-maintainer

Automate OpenClaw release preparation and validation across stable and beta channels.

Community
Advanced
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
daniel-heydari-devdaniel-heydari-dev

changelog-generation

Generate changelogs and enforce semantic versioning from conventional commits.

Community
Intermediate