What problem does it solve?
Game development teams often struggle to translate internal technical changelogs, git history, and sprint data into clear, engaging patch notes for players, a process that requires consistent tone, proper categorization, and elimination of internal jargon.
Core Features & Use Cases
- Automated Change Translation: Converts technical developer language (e.g., "refactored damage calculation pipeline") into player-friendly descriptions (e.g., "Improved hit detection accuracy").
- Flexible Output Styles: Supports brief, detailed, and full patch note formats, plus custom template detection for brand-aligned output.
- Multi-Source Data Aggregation: Pulls change data from internal changelogs, git logs, sprint retrospectives, and balance change documents to ensure no updates are missed.
- Use Case: A game studio releasing version 1.2.0 can use this skill to quickly generate consistent, on-brand patch notes without manually rewriting every technical change.
Quick Start
Use the patch-notes skill to generate player-facing patch notes for version 2.1.0 of your game.