patch-notes

To generate player-facing patch notes, the Skill collects git history and sprint data, translating developer language into categorized highlights, fixes, and known issues for the community. It organizes the output into categories like New Content, Quality of Life, and Bug Fixes.

Yes, you can apply tone guidance to changelog generation by specifying a style argument like detailed, allowing the Skill to detect writing preferences and format the release communication accordingly. It optionally uses an existing patch-notes template to match your desired tone.

The best way to translate developer changelogs into community manager release notes is to parse multi-source change data and categorize it into player experience updates. The Skill converts technical entries into actionable output like Gameplay Changes, Performance, and Known Issues.

Patch notes generation can work without a dedicated changelog file by falling back to git log history to gather change data for a specified release version. However, execution will block if all changelog sources are completely missing.

To save generated patch notes to versioned docs, the Skill optionally writes the categorized output directly to your documentation and internal archives after gathering and translating the release data. This satisfies release communication workflow requirements.

Yes, you can include before and after balance values in gameplay changes patch notes to provide clear context for player experience updates. The Skill supports optional balance value formatting when translating internal developer data into player language.