patch-notes

To generate player-friendly patch notes, aggregate changes from git history, sprint retrospectives, and balance documents, then translate developer language into clear player communication. The Skill parses technical changes and categorizes them into New Content, Gameplay Changes, Quality of Life, Bug Fixes, Performance, and Known Issues.

The best way to categorize game balance changes for a release changelog is to parse internal balance documents and apply them across release contexts. The output categorizes changes into Gameplay Changes and includes before/after values for balance when available.

You can customize patch notes by selecting from brief, detailed, or full style variants. These formats allow you to tailor the output specifically for players and stakeholders depending on the level of detail required.

To translate technical developer language into player communication, the Skill parses code changes and sprint data, then applies style-tailored output requirements. It satisfies language translation requirements to ensure clear communication for players.

Patch note generation works with sprint retrospective data by assembling notes from sprint data, git history, and balance documents. It aggregates these sources to automatically convert technical changes into a player-friendly summary.

To start creating patch notes, you need to provide the release version and your preferred style variant. The Skill will then process your aggregated changes and generate the corresponding categorized output.