skills.rest
navyapdh11
navyapdh11COMMUNITY
Explore all skills by this author →
GitHub

release-changelog

Generate stable release changelogs from commits, changesets, and PRs.

Updated Apr 24, 2026
Search Tags:#automation#git#changelog#changesets#release-notes#calver
One-click install
npx skills add https://github.com/navyapdh11/navya-cleaning-april --skill release-changelog-navyapdh11
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/navyapdh11/navya-cleaning-april/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/navyapdh11/navya-cleaning-april --skill release-changelog-navyapdh11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers auto-generate a user-facing release changelog by aggregating commits, changesets, and merged PR context since the last stable tag.

Core Features & Use Cases

  • Generate a user-facing changelog for stable releases by reading git history, changesets, and merged PRs.
  • Enforce structured sections (Breaking Changes, Highlights, Improvements, Fixes, Upgrade Guide) and output a single changelog file.
  • Provide a template for review and distribution without overwriting existing artifacts unless approved.

Quick Start

Generate the changelog by scanning git commits since the last stable tag, changesets, and merged PRs, and write to 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 generate stable release notes from git commits and changesets?▼

To generate stable release notes, you aggregate git history, .changeset files, and merged PR metadata since the last stable tag. The output is a single structured changelog file formatted with CalVer versioning, covering Breaking Changes, Highlights, Improvements, and Fixes.

How do I aggregate changesets and merged PR context for user-facing release notes?▼

You aggregate changesets and merged PR context by reading repository history and .changeset files since the last release. This compiles user-facing release notes into a single markdown file, enforcing structured sections like Breaking Changes, Improvements, and Upgrade Guides.

Can I use this to create a changelog without overwriting existing release artifacts?▼

Yes, this provides a template for review and distribution without overwriting existing artifacts unless explicitly approved. It safely generates the changelog file formatted to the specified CalVer format, ensuring your previous release notes remain intact during the process.

What sections are included when generating a changelog from git history?▼

Generating a changelog from git history includes structured sections for Breaking Changes, Highlights, Improvements, Fixes, and an Upgrade Guide. It reads commits and PR metadata to populate these categories, ensuring consistent, user-facing release documentation.

Related Skills

Explore More Software Engineering Skills→
bychrisrbychrisr

release-changelog

Generate structured Markdown changelogs from git history, changesets, and merged pull requests.

Community
Advanced
shellicarshellicar

github-release

Create GitHub releases from version tags to trigger npm-publish workflows.

Community
Advanced
getliengetlien
2

changeset

Analyze Git commits to generate structured changeset files for package versioning.

Official
Advanced
HomericIntelligenceHomericIntelligence
18

generate-changelog

Generate markdown changelog entries from git commit messages.

Official
Intermediate