patch-notes

This Skill generates player-facing patch notes by parsing git history, changelogs, and sprint notes, categorizing technical commits into player-ready markdown descriptions while preserving numeric balance values.

The best way to categorize game development changes is classifying git commits and balance documents into New Content, Gameplay Changes, Quality of Life, Bug Fixes, Performance, and Known Issues, translating technical jargon into player-friendly text.

Yes, you can use custom templates and tone guides to format release notes. The Skill detects these files and supports brief, detailed, and full styles to output categorized markdown suitable for publishing to players.

Yes, generating patch notes from git logs requires read access to repository files and git logs to parse changelog files, sprint retrospectives, and balance documents. Optional tone or template files can also be read.

You save generated patch notes to a repository archive by writing the final categorized markdown directly to docs/patch-notes and production/releases directories for long-term archival and production tracking.