skills.rest
brand6
brand6COMMUNITY
Explore all skills by this author →
GitHub

day-one-patch

Define and execute a controlled first-day patch with rollback and QA gating.

Updated Apr 22, 2026
Search Tags:#automation#rollback#qa#patch#release-management#risk-management#bug-fix
One-click install
npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill day-one-patch-brand6
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: day-one-patch
Source: https://github.com/brand6/Claude-Code-Game-Studios-zh-auto/tree/main/.claude/skills/day-one-patch
Command: npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill day-one-patch-brand6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines and guides the first-day patch process to address known issues securely, scoped to release windows and with a rollback plan, ensuring minimal risk before public launch.

Core Features & Use Cases

  • Defines solid patch scope, prioritization rules, and QA gating for post-release issues.
  • Produces a structured, auditable patch plan and a rollback strategy for all platforms.
  • Supports coordination across lead programmer, qa-tester, and release-manager roles to deliver a minimal, safe fix.

Quick Start

Initiate the day-one patch workflow for the current release and define its scope according to the guidelines.

Frequently Asked Questions about day-one-patch

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

FAQPage Schema
How do I plan a safe day-one patch for a game release?▼

A safe day-one patch requires defining strict patch boundaries, scoping fixes under four hours, and establishing a rollback strategy to ensure minimal risk before public launch. It coordinates QA gating and specialized sub-agents to produce an auditable patch record.

What is the best way to scope bug fixes for a tight release window?▼

Scoping bug fixes for tight release windows involves isolating critical certification feedback and post-release issues, then limiting the patch scope to changes executable within four hours. This minimizes new risk while addressing known problems effectively.

How do I create a rollback plan for a game patch?▼

Creating a rollback plan involves building a structured strategy for all platforms before executing the patch. This ensures that if the day-one patch introduces new issues or fails QA gating, the game can safely revert to its pre-patch state without risk.

Does this day-one patch process support coordination across QA and lead programmer roles?▼

Yes, the day-one patch process supports coordination across lead programmer, qa-tester, and release-manager roles. It uses specialized sub-agents to manage these workflows, ensuring the delivery of a minimal and safe fix with structured records.

When should I not execute a day-one patch?▼

You should avoid a day-one patch if the required bug fixes exceed the four-hour scoping window or lack a clear rollback strategy. Pushing changes without proper QA gating introduces significant new risk to the game release.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

day-one-patch

Scope and plan a rollback-first day-one patch for critical P1/P2 game bugs.

Community
Advanced
apexbusiness-systemsapexbusiness-systems
4

one-pass-debug

Diagnose code issues through a seven-phase debugging process.

Community
Advanced
polsegupolsegu

day-one-patch

Scope, prioritize, implement, and QA-gate urgent post-gold-master game fixes.

Community
Advanced
jovermierjovermier
1

quality-severity

Classify issues and code review findings into P1, P2, or P3 severity levels.

Community
Basic