update_changelog

Generate a day-grouped CHANGELOG.md from git commit history with status markers.

38|7|Updated May 3, 2026

Search Tags:#changelog #summarization #documentation #release notes #git history #repository maintenance #code evolution

Ready to run

npx skills add https://github.com/theafh/ai-modules --skill update-changelog-theafh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update_changelog
Source: https://github.com/theafh/ai-modules/tree/main/plugins/ai_dev/skills/update_changelog
Command: npx skills add https://github.com/theafh/ai-modules --skill update-changelog-theafh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

update_changelog turns scattered git commit history into a consistent, human-readable CHANGELOG.md that stays current without manually summarizing every day of work.

Core Features & Use Cases

Day-grouped changelog from git history: Creates or refreshes CHANGELOG.md with entries grouped strictly by calendar day (newest-first).
Status markers that evolve over time: Marks each logical change as [active], [changed later], or [superseded] by reevaluating against the current code state.
Repository-aligned summaries: Produces concise, past-tense descriptions focused on what changed, plus an explicit list of files touched per day.
Typical use case: After active development, refresh the repository’s CHANGELOG.md so release notes reflect reality.

Quick Start

Use update_changelog when you want the AI to refresh or backfill the repository root CHANGELOG.md from git history.

Frequently Asked Questions about update_changelog

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

FAQPage Schema

How do I generate a changelog from git commit history?▼

To generate a changelog from git commit history, this Skill derives logical change summaries and file touch lists to create a day-grouped CHANGELOG.md. It groups entries strictly by calendar day, ordering them newest-first.

What is the best way to maintain release notes from repository evolution?▼

Maintaining release notes from repository evolution involves reevaluating past entries against the current code state. This Skill marks each change as [active], [changed later], or [superseded] to ensure documentation reflects the latest code state.

How do I backfill a CHANGELOG.md while preserving implementation dates?▼

Backfilling a CHANGELOG.md while preserving implementation dates requires deriving summaries from historical git commits. The Skill generates per-day sections ending with horizontal rules, keeping entries ordered newest-first.

Can I automate changelog summarization for a repository without manual entry?▼

Automating changelog summarization without manual entry is possible by deriving concise, past-tense descriptions directly from git history. The Skill produces an explicit list of files touched per day alongside a fixed header and legend.

Does updating a changelog from git history overwrite existing formatting?▼

Updating a changelog from git history enforces strict output format compliance with a fixed header and legend. It organizes per-day sections ending with horizontal rules, ensuring consistent formatting across the entire document.

When do I need to refresh a repository changelog?▼

You need to refresh a repository changelog after active development to ensure release notes reflect reality. This process turns scattered git commits into a consistent, human-readable CHANGELOG.md grouped by calendar day.