What problem does it solve? Translating internal developer changelogs, git commits, and sprint records into clear, engaging patch notes that players actually understand is time-consuming and error-prone. This Skill automates that translation, categorizing changes and rewriting technical jargon into player-friendly language. ## Core Features & Use Cases - Multi-source change gathering: Reads internal changelogs, docs/CHANGELOG.md, git log between release tags, sprint retrospectives, and balance documents. - Automatic categorization and translation: Groups changes into New Content, Gameplay Changes, Quality of Life, Bug Fixes, Performance, and Known Issues, converting developer language into player-facing descriptions while preserving balance before/after values. - Style and tone control: Supports brief, detailed, and full output styles, detects custom tone guides and patch notes templates, and saves results to docs/patch-notes/ with an internal archive copy. - Use Case: Before shipping version 1.2.0 of your game, run the Skill to compile all merged changes since the last tag into a polished, categorized patch notes draft ready for community review. ## Quick Start Generate detailed patch notes for version 1.2.0 from the git history and changelog, then save them to the docs folder.
