What problem does it solve? Writing release notes that players actually understand is tedious: developers must dig through git logs, changelogs, and sprint retrospectives, then translate internal jargon into clear player communication. This Skill automates that entire pipeline. ## Core Features & Use Cases - Multi-source change gathering: Collects changes from internal changelogs, git log between release tags, sprint retrospectives, balance documents, and QA bug records. - Automatic categorization: Sorts changes into New Content, Gameplay Changes, Quality of Life, Bug Fixes, Performance, and Known Issues. - Developer-to-player translation: Converts technical language (e.g., "refactored damage calculation pipeline") into player-friendly phrasing ("improved hit detection accuracy") while preserving balance numbers. - Three output styles: brief (bullet points), detailed (with context and balance tables), and full (adds developer commentary). - Use Case: Before shipping version 1.2.0 of your game, run the skill to produce a complete patch notes document saved to production/releases/1.2.0/patch-notes.md, ready for your community channels. ## Quick Start Ask the AI to generate detailed patch notes for version 1.2.0 using the patch-notes skill.
