patch-notes

You can generate player-facing patch notes by feeding release changelogs, git history, sprint context, balance documents, and QA bug records into the patch-notes workflow. It translates technical developer language into clear, categorized communication for players.

To translate git commits into non-technical release communication, the patch-notes process reframes internal descriptions into clear explanations. It preserves key before and after balance numbers while removing jargon from developer changelog entries.

Yes, you can create brief, detailed, or full changelog summaries for game releases. The patch-notes generation supports multiple style outputs and can automatically save the formatted results to documentation and release archives.

Yes, the patch notes generator requires YAML-frontmatter-defined inputs to process changelog data. It validates that changelog data exists and will block the generation process if the required data is missing.

Tone guidance for release documentation works by detecting tone and templates from existing project docs. The patch-notes workflow then applies this detected style to ensure consistent, categorized, and player-appropriate messaging across all outputs.

If QA bug records or balance change docs are missing, generation proceeds using available sources like git history and release changelogs. However, the process strictly blocks execution if the core changelog data itself does not exist.