Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.
When this skill is invoked:
Parse the arguments:
version: the release version to generate notes for (e.g., 1.2.0)--style: output style — brief (bullet points), detailed (with context),
full (with developer commentary). Default: detailed.Gather change data from multiple sources:
production/releases/[version]/changelog.md if it existsgit log between the previous release tag and current tag/HEADproduction/sprints/ for contextdesign/balance/Categorize all changes into player-facing categories:
Translate developer language to player language:
Generate the patch notes using the appropriate style:
# Patch [Version] — [Title]
**New**
- [Feature 1]
- [Feature 2]
**Changes**
- [Balance/mechanic change with before → after values]
**Fixes**
- [Bug fix 1]
- [Bug fix 2]
**Known Issues**
- [Issue 1]
# Patch [Version] — [Title]
*[Date]*
## Highlights
[1-2 sentence summary of the most exciting changes]
## New Content
### [Feature Name]
[2-3 sentences describing the feature and why players should be excited]
## Gameplay Changes
### Balance
| Change | Before | After | Reason |
| ---- | ---- | ---- | ---- |
| [Item/ability] | [old value] | [new value] | [brief rationale] |
### Mechanics
- **[Change]**: [explanation of what changed and why]
## Quality of Life
- [Improvement with context]
## Bug Fixes
### Combat
- Fixed [description of what players experienced]
### UI
- Fixed [description]
### Networking
- Fixed [description]
## Performance
- [Improvement players will notice]
## Known Issues
- [Issue and workaround if available]
Includes everything from Detailed, plus:
## Developer Commentary
### [Topic]
> [Developer insight into a major change — why it was made, what was considered,
> what the team learned. Written in first-person team voice.]
Review the output for:
Save the patch notes to production/releases/[version]/patch-notes.md,
creating the directory if needed.
Output to the user: the complete patch notes, the file path, a count of changes by category, and any internal changes that were excluded (for review).