changelog-updater

Update CHANGELOG.md with categorized release notes from git commit history.

44|1|Updated Jan 21, 2026

Search Tags:#automation #git #changelog #developer tools #documentation #release notes

Ready to run

npx skills add https://github.com/cameroncooke/skills --skill changelog-updater-cameroncooke

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating your project's CHANGELOG.md file by analyzing git history and generating user-facing release notes.

Core Features & Use Cases

Automated Release Notes: Generates concise Added / Changed / Fixed / Breaking sections based on commit messages.
Commit Analysis: Compares commits between the latest tag and main to identify relevant changes.
Prerelease Handling: Correctly merges changes from prerelease tags into the canonical release section.
Contributor Attribution: Identifies and attributes external contributors.
Use Case: After merging a new feature and several bug fixes into main, use this Skill to automatically update your CHANGELOG.md with clear, user-friendly descriptions of the changes.

Quick Start

Use the changelog-updater skill to update the changelog for the next release.

Frequently Asked Questions about changelog-updater

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

FAQPage Schema

How do I automatically generate release notes from git commit history?▼

Automated release notes generation from git commit history analyzes commit deltas between the latest tag and main, categorizing changes into Added, Changed, Fixed, and Breaking sections for your changelog. This process extracts user-facing descriptions directly from commit messages.

What is the best way to keep a CHANGELOG up to date after merging features and bug fixes?▼

Keeping a CHANGELOG up to date is best handled by comparing git commits between the latest tag and the main branch, automatically categorizing changes into Added, Changed, Fixed, and Breaking sections to produce clear release notes.

Does changelog generation work with prerelease tags and external contributor attribution?▼

Changelog generation correctly handles prerelease tags by merging changes from prerelease tags into the canonical release section, and it identifies external contributors to provide accurate contributor attribution in the final release notes.

How do I categorize git commits into Added, Changed, Fixed, and Breaking sections for documentation?▼

Categorizing git commits into Added, Changed, Fixed, and Breaking sections involves analyzing commit message deltas between the latest tag and main, automatically sorting changes to generate structured user-facing documentation.

Can I update CHANGELOG.md by analyzing commit deltas without manual entry?▼

Updating CHANGELOG.md by analyzing commit deltas automatically derives user-facing release notes from git commit history, comparing the latest tag with main to populate Added, Changed, Fixed, and Breaking sections without manual entry.