changelog-generator

Parse conventional commits to generate Keep a Changelog-style entries.

Updated Apr 16, 2026

Search Tags:#automation #git #changelog #release-management #ci #conventional-commits

Ready to run

npx skills add https://github.com/ejoliet/claude-skills --skill changelog-generator-ejoliet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/ejoliet/claude-skills/tree/main/changelog-generator
Command: npx skills add https://github.com/ejoliet/claude-skills --skill changelog-generator-ejoliet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of release notes by turning Conventional Commit messages into a Keep a Changelog-style entry, reducing manual drafting and ensuring consistency.

Core Features & Use Cases

Parse conventional commits to categorize changes (Added, Fixed, Changed, etc.).
Generate markdown or JSON changelog entries from git ranges or direct input.
Optionally prepend the generated entry into an existing CHANGELOG.md for CI workflows.

Quick Start

Run the changelog-generator against your Git range or commit list to produce a formatted entry.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema

How do I generate a changelog from Conventional Commits?▼

To generate a changelog from Conventional Commits, parse your commit history using tag ranges or direct input to automatically categorize changes into Keep a Changelog-style sections like Added, Fixed, and Changed. The tool outputs formatted markdown or JSON entries.

Can I prepend generated release notes into an existing CHANGELOG.md in CI pipelines?▼

Yes, you can prepend generated release notes into an existing CHANGELOG.md for CI workflows. The generator optionally inserts the newly created Keep a Changelog-style entry directly at the top of your file during the pipeline run.

Does this changelog generator work with monorepos and multiple git tag ranges?▼

Yes, the changelog generator works across monorepos and CI pipelines by converting commit streams from specific git tag ranges into sectioned changelog entries. It processes commit history from your defined ranges to produce accurate release notes.

What is the best way to automate release notes from git commit history?▼

Automating release notes from git commit history is best achieved by parsing Conventional Commits to infer semantic version bumps and categorize changes. This process converts commit streams into structured Keep a Changelog-style markdown or JSON output automatically.

Do I need Conventional Commits to use this automated changelog generator?▼

Yes, you need Conventional Commits formatted messages to use this automated changelog generator effectively. The parsing logic relies on conventional commit types like feat or fix to categorize changes and infer semantic version bumps for the changelog entry.

Why are my git commits not categorizing correctly in the generated changelog?▼

Git commits may not categorize correctly in the generated changelog if they lack proper Conventional Commits formatting. The parser requires standard prefixes like feat, fix, or chore to accurately sort changes into Keep a Changelog sections and infer semantic bumps.