patch-notes

Generate player-facing patch notes by feeding git history, internal changelogs, and sprint retrospectives into an automated processor that categorizes and translates developer changes into clear community communications. The system reads repository changelogs and release notes to assemble change candidates automatically.

Yes, you can translate developer changelog entries into categorized release notes by classifying items into New Content, Gameplay Changes, Quality of Life, Bug Fixes, Performance, and Known Issues, converting technical jargon into language players understand.

This patch notes generator works with sprint retrospectives, production release directories, repository changelogs, and git logs to aggregate change candidates. It requires access to these internal development artifacts to assemble and translate them into player communications.

The best way to format release notes from internal changelogs is producing Brief, Detailed, or Full output styles. This approach detects project tone guides and templates to ensure consistent voice and can save both public and internal copies to designated docs paths.

You do not need a patch-notes template as it is optional, but providing one helps maintain a consistent tone. The system detects project tone guides and templates automatically and applies them to ensure your release notes have a structured voice.

Release notes drafts contain developer jargon when raw git logs are not translated through a categorization and tone detection process. Translating developer wording into player-facing language requires classifying items and applying project tone guides to strip technical terminology.