changelog-generator

Generate a CHANGELOG.md file from git commit history using Keep a Changelog format.

35|5|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/glincker/claude-code-marketplace --skill changelog-generator-glincker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/glincker/claude-code-marketplace/tree/main/skills/automation/changelog-generator
Command: npx skills add https://github.com/glincker/claude-code-marketplace --skill changelog-generator-glincker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation and updating of a CHANGELOG.md file, ensuring your project's release notes are consistently formatted and informative, saving developers significant time and effort.

Core Features & Use Cases

  • Automated Changelog Generation: Parses git commit history to create a CHANGELOG.md file adhering to the Keep a Changelog format.
  • Commit Categorization: Automatically groups commits into standard categories like Added, Changed, Fixed, Security, etc., based on Conventional Commits.
  • Use Case: After a development sprint, use this Skill to generate a comprehensive changelog that lists all new features, bug fixes, and improvements, ready for release.

Quick Start

Generate a CHANGELOG.md file from your git commit history.

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.md from git commit history?

You can generate a CHANGELOG.md from git commit history by parsing commit messages to categorize changes into Added, Changed, Fixed, and Security sections following the Keep a Changelog format. The tool links to issues, PRs, and commits automatically.

Does this changelog generator work with Conventional Commits?

Yes, this changelog generator fully supports Conventional Commits. It parses your conventional commit messages to automatically categorize changes into standard types like Added, Changed, Fixed, and Security, while detecting breaking changes for versioning.

How does automated changelog generation handle versioning and breaking changes?

Automated changelog generation handles versioning and breaking changes by parsing git commit history to detect breaking changes and managing version updates accordingly. It categorizes these changes into standard sections within the generated CHANGELOG.md file.

What is the best way to automate release notes from git commits?

The best way to automate release notes from git commits is using a tool that parses commit history to categorize changes into Added, Changed, Fixed, and Security types. This ensures consistently formatted release notes adhering to the Keep a Changelog standard.

Can I link issues and PRs in an automated CHANGELOG.md?

Yes, you can link issues and PRs in an automated CHANGELOG.md. The generator parses git commit history and automatically includes links to relevant issues, pull requests, and specific commits within the categorized changelog entries.

Do I need Conventional Commits to categorize changelog entries?

Yes, Conventional Commits are needed to automatically categorize changelog entries. The generator relies on parsing these structured commit messages to group changes into standard Keep a Changelog categories like Added, Changed, Fixed, and Security.