update-changelog

Aggregate commits since the latest git tag into the Unreleased section of CHANGELOG.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bytes032/agentkit --skill update-changelog-bytes032
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-changelog
Source: https://github.com/bytes032/agentkit/tree/main/skills/update-changelog
Command: npx skills add https://github.com/bytes032/agentkit --skill update-changelog-bytes032

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps changelog maintenance automatic by aggregating commit messages since the last release tag and populating the Unreleased section, ensuring release notes are consistent and ready for publishing.

Core Features & Use Cases

  • Determine baseline version with the latest git tag and collect commits since that baseline.
  • Update CHANGELOG.md (or CHANGELOG) by inserting notable changes under an Unreleased section.
  • Use cases include preparing release notes for new versions, auditing changes before releases, and maintaining consistent changelog practices.

Quick Start

Run the skill to scan commits since the most recent tag and automatically update the Unreleased section of your CHANGELOG.md.

Frequently Asked Questions about update-changelog

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

FAQPage Schema
How do I automate changelog updates from git history?

Automate changelog updates by aggregating commit messages since the last release tag and inserting notable changes into the Unreleased section of your CHANGELOG.md file.

What is the best way to generate release notes from conventional commits?

Generate release notes by scanning git history for conventional commits since the latest tag, then automatically populating the Unreleased section of your changelog with a reproducible, human-readable summary.

Can I use this to update a plain CHANGELOG file instead of CHANGELOG.md?

Yes, the tool supports both CHANGELOG.md and plain CHANGELOG files, updating whichever format your software project uses while enforcing conventional changelog practices and release workflows.

How does the tool determine which commits to include in the Unreleased section?

It determines the baseline version using your latest git tag, then collects and aggregates all notable commits made since that baseline into the Unreleased section of your changelog.

Do I need existing release tags to populate the changelog automatically?

Yes, the tool relies on the latest git tag as a baseline to collect subsequent commits, meaning your repository needs existing release tags to establish the starting point for changelog aggregation.

When should I use an automated changelog aggregator instead of manual editing?

Use an automated changelog aggregator when preparing release notes for new versions, auditing changes before releases, or maintaining consistent changelog practices across frequent software releases.