changelog

Generate a Keep a Changelog-compliant CHANGELOG.md from Git history.

Updated Feb 7, 2026

Search Tags:#automation #git #workflow #changelog #documentation #release-notes #keep-a-changelog

Ready to run

npx skills add https://github.com/maggit/claude-workspace --skill changelog-maggit

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating consistent, well-structured changelogs from a project's git history, eliminating manual drafting and ensuring release notes are up-to-date.

Core Features & Use Cases

Automatic categorization: Classifies commits (Added, Changed, Fixed, Docs, etc.) to Keep a Changelog sections.
Keep a Changelog formatting: Outputs a CHANGELOG.md that adheres to the Keep a Changelog conventions, suitable for releases.
Scenarios: Create a changelog for a new release between two tags, or update an existing CHANGELOG.md when new commits arrive.

Quick Start

Run the changelog skill to generate or update CHANGELOG.md from the repository history.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I generate a changelog from git history automatically?▼

A Keep a Changelog format structures release notes into Added, Changed, Fixed, and Docs sections, which you can populate automatically by parsing git commit prefixes like feat, fix, or docs.

How do I categorize git commits into Keep a Changelog sections for release notes?▼

Git commits are categorized into Keep a Changelog sections by parsing conventional commit prefixes such as feat for Added or fix for Fixed, then formatting the grouped entries into a structured CHANGELOG.md.

Can I update an existing CHANGELOG.md with new commits from a git tag?▼

Yes, you can update an existing CHANGELOG.md by parsing new git commits between tags and inserting their categorized entries into the existing Keep a Changelog structure without losing previous release notes.

What is the best way to create release notes between two git tags?▼

The best way to create release notes between two git tags is to parse the commit history in that range, categorize each commit by its conventional prefix, and output a Keep a Changelog-formatted section for that release.

Do I need conventional commit prefixes to automate changelog creation?▼

Yes, conventional commit prefixes like feat, fix, or docs are required to automatically categorize git history into the Added, Changed, and Fixed sections of a Keep a Changelog-compliant output.