update-changelog

Updates repository changelogs with notable changes from git commits since the last release tag.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill update-changelog-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-changelog
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/update-changelog
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill update-changelog-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a changelog current requires manually reviewing git history, deciding which commits matter to users, and formatting entries consistently. This Skill automates that review by reading commits since the last release tag and drafting properly styled entries in the changelog's Unreleased section. ## Core Features & Use Cases - Automatic baseline detection: Finds the most recent git tag with git describe --tags --abbrev=0 when no baseline version is provided. - Curated entry writing: Filters out insignificant changes (typos, internal refactors) and orders entries by importance: breaking changes, features, then fixes. - Style preservation: Matches the existing changelog's heading format, bullet style, and spacing, appending to an existing Unreleased section rather than replacing it. - Use Case: Before shipping version 2.14.0, run this Skill to scan all commits since the 2.13.0 tag and add user-facing changes with PR references to the Unreleased section of CHANGELOG.md. ## Quick Start Update the changelog with all notable changes since the last release tag.

Frequently Asked Questions about update-changelog

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

FAQPage Schema
How do I update a changelog from git commits automatically?▼

Run this Skill to detect the most recent git tag, list commits since that tag with git log, and add notable user-facing changes to the Unreleased section of CHANGELOG.md. It filters out insignificant commits like typo fixes and internal refactors.

How do I find the last release version in a git repository?▼

Use git describe --tags --abbrev=0 to get the most recent tag, which serves as the baseline version. The Skill then runs git log <baseline>..HEAD to collect all commits made since that release.

What changes should be included in a changelog entry?▼

Include notable user-facing changes: features, fixes, and breaking changes, referencing pull request numbers when available. Exclude typo fixes, internal refactoring, dependency bumps, and minor documentation updates.

Does this work if my changelog file is named CHANGELOG instead of CHANGELOG.md?▼

Yes. If CHANGELOG.md does not exist, the Skill falls back to a file named CHANGELOG. It preserves whichever heading style the file uses, such as ## Unreleased or ## [Unreleased].

When should I not update the changelog?▼

Skip the changelog when the change is purely internal, such as test-only modifications or code restructuring with no user-facing effect, unless your repository rules explicitly require logging every change.