changelog-keeper

Name: changelog-keeper
Availability: InStock
Author: abhattacherjee

Generate and maintain CHANGELOG.md files from git commit history.

1|2|Updated Feb 24, 2026

Search Tags:#automation #git #changelog #documentation #release notes #commit history

Ready to run

npx skills add https://github.com/abhattacherjee/claude-code-skills --skill changelog-keeper

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually updating a CHANGELOG.md file is tedious and error-prone, often leading to outdated or incomplete release notes. This Skill automates the process, ensuring your changelog accurately reflects your project's evolution.

Core Features & Use Cases

Automated Entry Generation: Creates changelog entries directly from git commit history.
Categorization: Automatically categorizes changes (Added, Fixed, Changed, etc.) based on conventional commit prefixes or file paths.
Version Management: Supports updating the [Unreleased] section or creating versioned entries for releases.
Use Case: Before releasing a new version, run this Skill to generate a comprehensive changelog entry from your recent commits, ensuring users know exactly what's new.

Quick Start

Run the update-changelog.sh script with the --dry-run flag to preview the changelog entry.

Frequently Asked Questions about changelog-keeper

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

FAQPage Schema

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

You can automatically generate a changelog from git commit history by running a script that parses commits and categorizes them based on conventional commit prefixes. This creates accurate changelog entries without manual input.

What is the best way to keep CHANGELOG.md up-to-date before a release?▼

The best way to keep CHANGELOG.md up-to-date is to automate maintenance by parsing git commit history. This ensures your release notes accurately reflect project development with categorized entries.

How do conventional commit prefixes categorize changes in release notes?▼

Conventional commit prefixes categorize changes in release notes by mapping commit messages to categories like Added, Fixed, or Changed. This parsing logic automatically organizes git history into structured changelog entries.

Can I preview changelog entries before updating the actual file?▼

Yes, you can preview changelog entries before updating the file by running the update script with a --dry-run flag. This allows you to review generated release notes safely.

How do I manage unreleased versus versioned entries in a changelog?▼

You can manage unreleased versus versioned entries by configuring the changelog generation script to update the [Unreleased] section or create new versioned entries for specific releases.