changelog

Auto-generating release notes from git commits and sprint data requires aggregating commit history, sprint reports, and design documents into a structured format. This Skill consolidates those sources to produce cohesive changelogs for quick publishing.

You can create separate changelogs for internal teams and players from the same git history. The generator extracts changes, categorizes them, and formats dual outputs: an internal engineering-focused changelog and a player-facing release notes version.

Consolidating design docs and git commits into a single changelog involves automated aggregation from multiple sources. This Skill collects changes from git history, sprint reports, and design documents to form a cohesive, publish-ready document with consistent structure and tone.

Design documents are not strictly required but are supported as an input source. The changelog generator automates aggregation by collecting changes from git history, sprint reports, and design documents to form a cohesive summary for players.

Automated changelog generation categorizes git commits by implementing a deterministic workflow that extracts changes and sorts them. This process applies to release pipelines requiring both internal development notes and player-facing summaries across versions.