patch-notes

To convert git changelogs into player-facing patch notes, aggregate repository git history, docs/CHANGELOG.md, and sprint notes to generate categorized descriptions. The output translates technical commit entries into plain language across categories like Gameplay Changes and Bug Fixes.

Yes, you can generate game patch notes from sprint retrospectives and balance documents by reading design/balance files and QA records. The process categorizes changes into player-facing sections while preserving numeric balance values from the original design documents.

Automating release notes from git history involves reading version tags and commit ranges to produce brief, detailed, or full patch notes. This workflow maps developer language to user-facing categories and writes outputs to docs/patch-notes and production/releases directories.

You do not need a tone guide to generate patch notes from repository changelogs, but the workflow detects and applies optional tone or template files if present. It blocks generation entirely when no changelog data is available to prevent incomplete notes.

Categorizing patch notes from QA records and balance docs works by mapping internal change entries into player-facing categories such as New Content, Quality of Life, and Known Issues. Developer language is rewritten into plain descriptions while numeric balance values are preserved.

When generating public patch notes from git history, internal changes are excluded from the final output. The workflow presents a draft with change counts and excluded internal entries, then prompts for approval before writing public and internal files.