update-changelog

Compile notable commits since the last git tag into the Unreleased section of CHANGELOG.md.

Updated Mar 12, 2026

Search Tags:#changelog #release notes #git tags #documentation automation #commit summarization #unreleased section

Ready to run

npx skills add https://github.com/mpsuesser/workspace --skill update-changelog-mpsuesser

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-changelog
Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/pi/agent/skills/update-changelog
Command: npx skills add https://github.com/mpsuesser/workspace --skill update-changelog-mpsuesser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent outdated or incomplete changelogs by automatically collecting user-relevant changes that occurred since the last release and adding them to the correct place.

Core Features & Use Cases

Detects the baseline version: Uses a provided baseline version or falls back to the most recent git tag to define the changelog window.
Scans commits since the baseline: Gathers commit information from git log <baseline>..HEAD to identify what has changed.
Updates the right changelog file: Writes to CHANGELOG.md or uses CHANGELOG if CHANGELOG.md is missing.
Writes only to Unreleased: Ensures all added entries appear only under the existing or newly created "Unreleased" section, preserving the repo’s existing style.
Filters for user-impacting changes: Includes notable features, fixes, and breaking changes while ignoring insignificant refactors and minor documentation/typo work.

Quick Start

Ask your AI to update the changelog by reading changes since the most recent git tag and appending only user-relevant items to the Unreleased section of CHANGELOG.md (or CHANGELOG if needed).

Frequently Asked Questions about update-changelog

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

FAQPage Schema

How do I automatically update my changelog with recent git commits?▼

Automatically update your changelog by parsing commits from the last git tag to HEAD and appending only user-relevant entries to the Unreleased section of CHANGELOG.md or CHANGELOG.

How does commit summarization work for release notes generation?▼

Release notes generation works by parsing commits between a baseline version and HEAD, filtering for user-impacting features and fixes while ignoring minor refactors, and writing them under an Unreleased section.

Can I generate an Unreleased section in CHANGELOG.md if the file does not exist yet?▼

Yes, if CHANGELOG.md is missing, the changelog update process uses CHANGELOG or creates a new file, ensuring an Unreleased section is established to capture new user-significant entries.

Do I need a specific git tag to define the changelog window?▼

No, you do not need a specific git tag if you provide an explicit baseline version; otherwise, the process automatically falls back to the most recent git tag to define the changelog window.

What's the best way to filter out insignificant commits from changelog entries?▼

The best way to filter insignificant commits is to include only notable features, fixes, and breaking changes while ignoring insignificant refactors and minor documentation or typo work when summarizing git log history.

Will updating the changelog overwrite my existing release notes formatting?▼

No, updating the changelog preserves your repository's existing style and only adds new user-impacting entries to the existing or newly created Unreleased section without altering past release notes.