day-one-patch

Scope, implement, and gate a day-one game patch with rollback planning.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill day-one-patch-rakhnianskii9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: day-one-patch
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/day-one-patch
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill day-one-patch-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Day-one patch planning and gating for game releases, providing a disciplined workflow to scope, implement, and QA a focused update with a built-in rollback.

Core Features & Use Cases

  • Phase-driven patch planning: gather release context, classify scope, and define a minimal viable patch.
  • Rollback-first discipline: establish rollback procedures before any code changes to minimize post-launch risk.
  • Patch-record to deployment: generate a structured patch notes/record for traceability and approvals.

Quick Start

Run the day-one patch workflow to load the current release context, scope the patch, and prepare the rollback plan before any fixes.

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 day-one patch for a game release?

A day-one patch workflow scopes, implements, and gates a focused game update alongside a rollback plan. It applies to release contexts with gold masters and cert gates, specifying when to fix, what to fix, and how to verify changes during a single patch window.

What is rollback-first discipline in patch management?

Rollback-first discipline in patch management requires establishing formal rollback procedures before any code changes are made. This minimizes post-launch risk by ensuring a verified recovery path exists prior to deploying a day-one patch.

How do I scope minimum viable changes for a game patch?

Scope minimum viable changes by gathering release context and classifying the scope to define a minimal viable patch. This phase-driven planning ensures only necessary fixes are included during a single patch window.

Does day-one patch planning work with gold master and cert gates?

Yes, day-one patch planning explicitly applies to release contexts with gold masters and cert gates. The workflow specifies requirements for lightweight QA and formal rollback documentation to verify changes during a single patch window.

How do I generate traceable patch notes for a release?

Generate traceable patch notes by creating a structured patch-record from the scoped fixes and rollback plan. This documentation flows from patch-record to deployment, providing traceability and formal approvals before the update is released.