update_changelog

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.

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.

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.

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.

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.

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.