
Day-One Patch Planner
Plans and gates a small post-gold-master launch patch with QA checks and a rollback plan
- Repository
- Donchitos/Claude-Code-Game-Studios
- Stars
- 32,965
- Licence
- MIT
- Files
- 1 file
What it does
When installed, the agent helps a game team prepare a small fix-only patch to ship on launch day, after the release build is locked. It checks that a release gate was passed, lists which known bugs are safe to fix quickly, defers larger work to a later patch, and requires a written rollback plan before any code changes. Code changes go through approval steps and specialist sub-agents, followed by a targeted QA pass.
Great for
- Game studios preparing a day-one patch after a gold master build
- Producers and release managers who want a documented scope and rollback plan
- Teams using the Claude Code Game Studios framework who need a structured release workflow
Skip it if
- Projects not yet in Release or Polish stage, since the skill stops early for those
- Teams without a passed release gate record, since the skill's reduced QA scope depends on that gate and it will stop or ask for a full QA pass instead
- Non-game software, because the workflow assumes game platforms, cert builds and a studio folder structure
Try asking
- “Plan a day-one patch for our gold master build, limited to known-bugs scope”
- “Scope the cert feedback fixes for our console submission into a day-one patch”
- “Write the rollback plan for our Release-stage build before we fix anything”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
day-one-patch.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip day-one-patch.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip day-one-patch.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
- Run the release gate check first so the skill finds a passing gate record; without one it will stop or switch to a full QA pass.
- Keep bug reports in production/qa/bugs/ with reproduction steps and affected files, since the skill relies on them to scope fixes.
- Review the proposed scope table carefully and keep items to what can be fixed in under a day; the skill itself warns against bloated patches.
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.