patch-notes

Generate player-facing patch notes by aggregating git history, changelog files, sprint context, and QA records for a specific version, then translating developer wording into categorized player messaging. The tool parses a version argument and applies tone guidance to format the output.

Translating internal developer changelogs into community update messaging involves detecting available style templates, converting technical changes into player language, and grouping items into categories like New Content, Gameplay Changes, Quality of Life, and Bug Fixes while preserving balance values.

Release communication tone and format can be customized using available style guidance and patch-notes templates. When no template is present, the tool falls back to built-in brief, detailed, or full formats to suit different player audiences.

Patch notes generation can proceed without dedicated balance documents or sprint retrospectives by relying on available changelog files and git history. However, it blocks execution as a fallback when core changelog sources are entirely missing for the specified version.

Save generated patch notes to versioned documentation automatically by providing a version argument such as 1.2.0 in the command. The tool generates categorized output and optionally writes the player-ready notes to corresponding versioned doc files.

Patch notes generation results may miss balance value changes if the source balance documents are absent or lack before/after values. The tool preserves these values during translation, so incomplete source data directly affects the output accuracy.