day-one-patch

Classify open bugs and cert feedback into an approved mini-sprint patch scope.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill day-one-patch-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: day-one-patch
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/day-one-patch
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill day-one-patch-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents launch-day chaos by scoping and validating a focused day-one patch that fixes only what is safe and necessary, with QA sign-off and a rollback plan before any changes ship.

Core Features & Use Cases

  • Patch scoping from real release signals: Loads release stage, gate verdicts, open/verified bugs, recent sprints, and security audit status to determine what belongs in the day-one patch.
  • Mini-sprint discipline with approvals: Classifies bugs by severity/priority/risk, then asks you to approve or adjust the proposed patch scope and enforces a safe time budget.
  • Rollback plan first: Requires a platform-aware rollback procedure to be written before any implementation begins.
  • Implementation + targeted QA gate: Coordinates focused fixes and then runs a lightweight QA pass (targeted smoke or broader regression) limited to changed areas, requiring a PASS or PASS WITH WARNINGS verdict.
  • Produces a complete internal patch record: Writes the internal patch record and supports generating player-facing patch notes and verification/closure for fixed bugs.

Quick Start

Run the day-one patch with the default patch scope by asking: "Prepare a day-one patch scope for known bugs for version X and write the patch record after QA gate."

Frequently Asked Questions about day-one-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scope a safe day-one patch after a game reaches gold master?

Scoping a safe day-one patch involves classifying open bugs and cert feedback by severity and risk, then approving a mini-sprint scope that strictly avoids new features and risky refactors to ensure launch stability.

What is a day-one patch rollback plan and when do I need to write it?

A day-one patch rollback plan is a platform-aware recovery procedure required before any implementation begins. You need it when shipping post-gold-master fixes to safely revert changes if the patch causes launch-day issues.

How do I run QA gating for a day-one patch without delaying the launch?

Run QA gating for a day-one patch by executing a lightweight, targeted smoke or regression test limited strictly to changed areas, requiring a final PASS or PASS WITH WARNINGS verdict before generating patch notes.

Can I include new features and bug refactors in a day-one patch sprint?

You cannot include new features or risky refactors in a day-one patch sprint. This stage focuses exclusively on classifying and fixing necessary open bugs and certification feedback to avoid introducing new launch-day risks.

How do I generate player-facing patch notes from an internal release record?

Generate player-facing patch notes from an internal release record by finalizing the scoped mini-sprint fixes and QA gate verdicts, then translating the verified production release record into user-ready communication.

What is the best way to triage cert feedback and open bugs for a launch readiness patch?

The best way to triage cert feedback and open bugs for a launch readiness patch is to load release stage signals, classify issues by priority and risk, and enforce a safe time budget within an approved mini-sprint scope.