changelog-gen

Generate CHANGELOG.md files from git history and pull requests.

19|4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill changelog-gen-andregusman-raiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-gen
Source: https://github.com/andregusman-raiz/a-gusman-claude/tree/main/skills/changelog-gen
Command: npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill changelog-gen-andregusman-raiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates CHANGELOG.md automatically from git history, conventional commits, and PRs between tags/releases using the Keep a Changelog format. This enables consistent release notes and change history for software projects.

Core Features & Use Cases

  • Automated changelog generation from git history, conventional commits, and PRs.
  • Keeps the document in Keep a Changelog format, with sections like Added, Changed, Fixed, and more.
  • Supports generating changelogs for specific tag ranges or HEAD, suitable for releases, release notes, and history documentation.

Quick Start

Ask the AI to generate or update a CHANGELOG.md from recent commits and PRs.

Frequently Asked Questions about changelog-gen

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

FAQPage Schema
How do I auto-generate a changelog from git history and pull requests?

To auto-generate a changelog from git history, this Skill parses conventional commits and PR data between tags or HEAD using git log and gh pr commands. It organizes entries into Keep a Changelog sections and writes the output directly to CHANGELOG.md.

Does changelog generation work with conventional commits and Keep a Changelog format?

Changelog generation works directly with conventional commits by parsing their types to populate Keep a Changelog sections like Added, Changed, and Fixed. This ensures release notes follow the standard format automatically from your commit history.

Can I generate release notes for a specific tag range or HEAD?

You can generate release notes for specific tag ranges or HEAD by configuring the git log scope. The Skill extracts commit and pull request data within those boundaries to produce an accurate Keep a Changelog document for that release.

What's the best way to maintain a CHANGELOG.md for consistent software release notes?

The best way to maintain a CHANGELOG.md for consistent release notes is to automate generation from git history and PRs. This Skill formats entries into standard Keep a Changelog sections, ensuring documented changes across releases without manual writing.

Do I need GitHub CLI to generate changelogs from pull request data?

You need GitHub CLI to generate changelogs from pull request data because the Skill uses the gh pr command to fetch PR details. It combines this PR data with git log history to build the final Keep a Changelog release notes document.

Why are my conventional commits not showing up correctly in the generated changelog?

If conventional commits are not showing up correctly in the generated changelog, verify your commit messages follow the conventional format strictly. The Skill parses these specific commit types to organize entries into appropriate Keep a Changelog sections.