skills.rest
santhank8
santhank8COMMUNITY
Explore all skills by this author →
GitHub

release-changelog

Generate a calver-aligned release changelog from commits, changesets, and merged PRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of user-facing changelogs for stable Paperclip releases by aggregating commits, changesets, and merged pull request context since the last stable tag, ensuring accuracy and consistency.

Core Features & Use Cases

  • Changelog generation: Consolidates commits, changesets, and PR context into a single, publish-ready document.
  • Calver-aligned output: Writes to releases/vYYYY.MDD.P.md matching Paperclip's stable versioning scheme.
  • Use Case: A team preparing a new stable release can generate a complete changelog without manual curation, ready for release notes.

Quick Start

Run the skill to generate the release changelog file at releases/vYYYY.MDD.P.md from recent commits, changesets, and merged PRs.

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 a changelog from git commits and changesets for a release?▼

Auto-generate a changelog by reading git history, .changeset files, and merged PR data since the last stable tag to produce a publish-ready document at releases/vYYYY.MDD.P.md. This consolidates all release context into a single file without manual curation.

What is a calver-aligned changelog and when do I need it for deployment?▼

A calver-aligned changelog organizes release notes by calendar versioning at releases/vYYYY.MDD.P.md. You need it during stable release planning to ensure version documentation matches your chronological deployment scheme and provides accurate user-facing context.

How to aggregate merged pull request context into release notes automatically?▼

Aggregate merged PR context by reading git history and pull request data since the last stable tag, consolidating commits and .changeset files into a single changelog file. This captures all relevant PR details for the release notes automatically.

Can I overwrite an existing changelog file when generating release notes?▼

Existing changelog files at releases/vYYYY.MDD.P.md are not overwritten unless explicitly instructed. This prevents accidental data loss during release planning while allowing forced regeneration when you need to replace previous content.

Does changelog generation work without manual curation for large release workflows?▼

Changelog generation works without manual curation by automatically aggregating commits, changesets, and merged PR context. It suits release planning and deployment workflows where teams need a complete, publish-ready changelog file efficiently.

Why does my generated changelog use the vYYYY.MDD.P.md format?▼

The vYYYY.MDD.P.md format aligns with the calver versioning scheme used for stable releases. This ensures the changelog file naming convention matches your chronological release tags and deployment versioning structure.

Related Skills

Explore More Software Engineering Skills→
kurokeitakurokeita
1

changelog-automation

Automate changelog generation from commits, PRs, and releases.

Community
Intermediate
kangnam7654kangnam7654
1

release-changelog

Generate a changelog file from git history, changesets, and PR metadata.

Community
Advanced
navyapdh11navyapdh11

release-changelog

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

Community
Intermediate
chiubakachiubaka
1

changesets-hygiene

Enforce .changeset entries and prevent manual version or changelog edits.

Community
Intermediate