
Patch Notes Writer
Turns a game's git history and changelogs into player-friendly patch notes
- Repository
- Donchitos/Claude-Code-Game-Studios
- Stars
- 32,965
- Licence
- MIT
- Files
- 1 file
What it does
When a game developer asks for patch notes for a version, the agent reads the project's git history, changelogs, balance docs and sprint notes, then rewrites developer jargon as plain language a player would understand. Before writing anything, it checks that the git history actually belongs to the game and filters out framework or tooling commits so they don't show up as player-facing changes. It can also pick up a team's tone guide or patch-notes template if one exists.
Great for
- Indie game developers who need release notes written for players rather than engineers
- Small studios using the Claude Code Game Studios framework who want consistent patch notes per version
Skip it if
- Projects with no git history or changelog data, since the skill stops and asks for those inputs
- Repos where the history is mostly framework or tooling work and the game's own commits are few, because the output may be thin or wrong; a human should review the result before publishing
Try asking
- “Write detailed patch notes for version 1.2.0”
- “Generate brief patch notes for 0.9.3 in bullet form”
- “Create full patch notes with developer commentary for the next release”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
patch-notes.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip patch-notes.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip patch-notes.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Pass a version number and a style flag (brief, detailed or full) to control the output
- Review the 'N of M commits used' count the skill reports to confirm the filter ran sensibly
- Add a docs/PATCH-NOTES-STYLE.md or template file so the output matches your studio's voice
What's inside
- SKILL.md
Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.