patch-notes

Generate player-facing patch notes by automatically aggregating internal changelogs, git history, and sprint data into readable communications. The system detects tone and applies templates to convert technical development updates into clear release notes for your players.

Converting sprint retrospectives into release notes involves aggregating internal balance docs and sprint files, then applying tone detection to create player-friendly communications. You can output the generated notes in Brief, Detailed, or Full styles depending on your audience needs.

Yes, you can include optional developer commentary when generating patch notes from internal changelogs. This feature allows you to add contextual insights directly within the Brief, Detailed, or Full style release notes created from your git history and design documents.

Patch note generation supports hotfixes, patches, and major updates by aggregating data from production releases and design docs. It automatically detects the appropriate tone and applies player-friendly templates to communicate changes across all release types.

You can create Brief, Detailed, or Full style release notes from internal balance docs and design notes. The system uses a built-in template system with tone detection to ensure the output maintains a player-friendly voice across different release formats.

Technical changelogs are often opaque because they use developer-specific language; you can fix this by using tone detection to convert them into player-facing patch notes. The system automatically translates internal git logs and sprint data into clear, player-friendly communications.