patch-notes

Generate player-facing patch notes by synthesizing internal changelogs, sprint context, QA records, and git history. The process translates developer language into clear player benefits, categorizing changes into sections like gameplay tweaks, quality of life improvements, and bug fixes.

Translate developer changelog jargon into clear player benefits by synthesizing internal documentation and applying tone adaptation. This process detects available style guidance to format output consistently with your community voice, removing unnecessary internal technical terms for player-ready release notes.

You can use a specific patch notes template to format output by applying tone and template adaptation. This detects available tone and style guidance from your configured documentation, ensuring the generated release notes categorize changes consistently with your established community voice.

When changelog data is missing, patch notes generation triggers a blocked-and-instructive fallback. This mechanism safely handles the absence of internal version-specific sources, sprint retrospectives, or git history, providing instructive guidance instead of failing or fabricating release information.

Patch notes generation supports balance changes by including accurate before and after balance values. It synthesizes QA records and internal balance documentation, translating these technical adjustments into clear, categorized gameplay changes for the player-facing release output.

Write generated patch notes to public and internal archive locations through publishing workflow support. After drafting the release notes and reviewing them for player relevance, the workflow offers to save the output to both public communication channels and internal documentation repositories.