release-changelog

Parse git commits between refs to draft a structured CHANGELOG entry.

6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/withpiper/pipekit --skill release-changelog-withpiper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/withpiper/pipekit/tree/main/skills/release-changelog
Command: npx skills add https://github.com/withpiper/pipekit --skill release-changelog-withpiper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts a structured CHANGELOG entry from git commits between release tags, saving time and ensuring consistency while preserving human judgment over the narrative.

Core Features & Use Cases

  • Bucket commits into sections (What's New, Fix, Documentation, Migration, Other Changes) based on conventional commit types.
  • Extract and surface issue references (closes #N, #N) for traceability.
  • Print a ready-to-edit draft to stdout with read-only guarantees on git state and CHANGELOG.md.

Quick Start

Review the draft output printed to stdout, copy it into CHANGELOG.md, and edit narrative sections as needed.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I generate a changelog draft from git commits automatically?

To generate a changelog draft from git commits, this Skill parses commit history between two refs and buckets changes into categories like What's New and Fix using conventional commits formatting. It outputs a structured draft to stdout for you to review and manually edit before publishing.

How does conventional commits formatting work for release notes?

Conventional commits formatting for release notes works by parsing commit messages and bucketing them into specific sections such as What's New, Fix, Documentation, Migration, and Other Changes. This ensures a structured and consistent changelog draft for human review.

Can I automatically write generated changelog entries directly to CHANGELOG.md?

You cannot automatically write generated changelog entries directly to CHANGELOG.md because the Skill enforces read-only guarantees on git state and files. It prints a ready-to-edit draft to stdout, guiding you to manually copy and edit the narrative sections into your file.

How do I extract issue references from git commits for changelog traceability?

To extract issue references from git commits for changelog traceability, the Skill parses commit messages to find references like closes #N and #N. It surfaces these references in the generated draft, linking the changes directly to their corresponding issues for review.

What is the best way to draft release notes from git tags without altering repository state?

The best way to draft release notes from git tags without altering repository state is to use a read-only parser that resolves version ranges between tags. This Skill generates a CHANGELOG draft in stdout while enforcing read-only guarantees on your git state and files.

Do I need to follow strict conventional commits to use this changelog generator?

You need to follow conventional commits to effectively use this changelog generator, as it relies on commit types to bucket changes into What's New, Fix, Documentation, Migration, and Other Changes. Commits not matching these types are grouped into Other Changes for manual sorting.