changelog-gen

Generate Keep a Changelog release notes from Git history.

9|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/d0d012/claude-trim --skill changelog-gen-d0d012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-gen
Source: https://github.com/d0d012/claude-trim/tree/main/testdata/demo/plugins/dev-tools/skills/changelog-gen
Command: npx skills add https://github.com/d0d012/claude-trim --skill changelog-gen-d0d012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps release notes up to date by transforming Git history into Keep a Changelog format, reducing manual effort and ensuring consistency across releases.

Core Features & Use Cases

  • Group commits by type (feat, fix, docs, breaking changes) into Keep a Changelog style sections.
  • Generate release notes for specified tags or HEAD, facilitating versioned releases.
  • Handle conventional commits to produce structured, publication-ready entries.

Quick Start

Generate the latest changelog for your repository in Keep a Changelog format.

Frequently Asked Questions about changelog-gen

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

FAQPage Schema
How do I generate release notes from Git history automatically?▼

Generate release notes from Git history automatically by reading conventional commits and grouping them by type, such as feat, fix, and docs, into a structured Keep a Changelog format. The tool outputs publication-ready entries for versioned releases.

How do conventional commits map to Keep a Changelog sections?▼

Conventional commits map to Keep a Changelog sections by grouping commit types like feat, fix, docs, and breaking changes into corresponding structured categories. This ensures release notes maintain consistent formatting across multiple versioned releases.

Can I generate a changelog for a specific Git tag or just the latest commits?▼

You can generate a changelog for a specific Git tag or HEAD to facilitate versioned releases. The tool processes conventional commits across specified tags to produce structured release notes in Keep a Changelog format.

Does this tool require conventional commits to format release notes?▼

Yes, the tool reads conventional commits to handle grouping by type and format release notes per Keep a Changelog standards. It applies to software projects with versioned releases and multiple commits across tags.

What is the best way to automate versioned release notes for multiple tags?▼

Automate versioned release notes for multiple tags by transforming Git history into Keep a Changelog format. This reduces manual effort and ensures consistency across releases by grouping conventional commits into structured, publication-ready entries.

How do breaking changes appear in the generated changelog?▼

Breaking changes appear in the generated changelog as a distinct grouped section alongside other conventional commit types like feat, fix, and docs. The tool formats these entries per Keep a Changelog standards for clear release notes.