forge-update-changelog

Update CHANGELOG.md with user-facing changes from recent commits.

65|5|Updated Feb 6, 2026

Search Tags:#automation #git #changelog #documentation #commits #release-notes

Ready to run

npx skills add https://github.com/mgratzer/forge --skill forge-update-changelog

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update CHANGELOG.md with user-facing changes from recent commits to keep release notes accurate and up-to-date.

Core Features & Use Cases

Collect recent commits since the last changelog update, identify user-facing changes (feat, fix, perf), and ignore internal-only edits.
Group changes into intuitive categories (New Features, Improvements, Bug Fixes, Performance) and generate concise, plain-language entries for end users.
Update the changelog at the top of the file with a timestamped section so teams and customers can see what changed.

Quick Start

Run the forge-update-changelog skill to parse recent commits and update CHANGELOG.md with user-facing changes.

Frequently Asked Questions about forge-update-changelog

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

FAQPage Schema

How do I automate changelog updates from recent git commits?▼

You can automate changelog updates by parsing recent git commits, filtering for user-facing changes like features and fixes, grouping them into categories, and writing a timestamped entry to the top of your changelog file.

What is the best way to generate release notes from conventional commit messages?▼

Generating release notes from conventional commits involves reading recent project commits, filtering for feat, fix, and perf prefixes, and grouping them into intuitive categories to produce concise, plain-language changelog entries.

How do I keep my CHANGELOG.md accurate for ongoing development cycles?▼

To keep your CHANGELOG.md accurate during development cycles, collect commits since the last update, identify user-facing changes, ignore internal-only edits, and prepend a new timestamped section with categorized release notes.

Can I filter internal-only commits when updating project documentation?▼

Yes, you can filter internal-only commits when updating documentation by selecting only user-facing changes such as feat, fix, and perf commits, while ignoring internal edits to generate plain-language entries for end users.

Does automated changelog generation work without external dependencies?▼

Yes, automated changelog generation can work without external dependencies by directly reading the current changelog file, gathering recent git commits, and writing grouped user-facing changes back to the file.

Why are my changelog entries not grouping into the correct categories?▼

Changelog entries may not group correctly if commit messages lack conventional prefixes like feat, fix, or perf, which are required to filter and categorize user-facing changes into New Features, Improvements, Bug Fixes, and Performance sections.