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 while preserving balance numbers and filtering out internal-only changes. ## Core Features & Use Cases - Multi-source change gathering: Reads internal changelogs, docs/CHANGELOG.md, git log between release tags, sprint retrospectives, and balance documents. - Player-language translation: Converts technical jargon (e.g., "refactored damage pipeline") into player-friendly phrasing (e.g., "improved hit detection accuracy") while keeping before/after balance values. - Style and tone control: Supports brief, detailed, and full output styles, auto-detects tone guides and custom templates, and blocks generation when no changelog data exists. - Use Case: Before shipping version 1.2.0 of your game, run the Skill to produce categorized patch notes with highlights, balance tables, bug fixes grouped by system, and known issues, saved to docs/patch-notes/1.2.0.md. ## Quick Start Use $ai-game-studio:patch-notes to generate detailed patch notes for version 1.2.0 from my changelog and git history.
