skills.rest
imgamer
imgamerCOMMUNITY
Explore all skills by this author →
GitHub

day-one-patch

Scope safe P1/P2 fixes into a day-one patch plan with rollback and QA gates.

Updated Dec 22, 2024
Search Tags:#bug triage#patch notes#rollback plan#cert feedback#game launch#build gating#release QA
One-click install
npx skills add https://github.com/imgamer/AILearn --skill day-one-patch-imgamer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: day-one-patch
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/day-one-patch
Command: npx skills add https://github.com/imgamer/AILearn --skill day-one-patch-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you prepare a day-one patch that fixes known, high-priority issues without scope creep, while ensuring a lightweight QA gate and a rollback plan exist before anything ships.

Core Features & Use Cases

  • Patch Scoping & Risk Control: Filters bugs for safe inclusion based on severity/priority and estimated effort (e.g., under 4 hours) and avoids new features or refactoring.
  • Release Readiness Validation: Confirms the project is in the correct Release/Polish stage and checks gate verdicts, open/verified bug status, sprint context, and security audit notes.
  • Rollback-First Governance: Requires a rollback plan to be produced and written before implementation begins, including platform constraints and rollback triggers.
  • Targeted Implementation & QA Gate: Coordinates implementation with a lead programmer and verifies fixes with a targeted smoke check or broader regression as needed.
  • Patch Record & Player Notes Outputs: Produces an internal patch record and then enables generation of player-facing patch notes and bug closure workflows.

Quick Start

Use the day-one-patch skill to prepare a day-one patch scope, implement approved fixes, run the required QA gate, and write the release record to production/releases/day-one-patch-[version].md.

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 launch?▼

To plan a day-one patch, scope known issues and cert feedback into a mini-sprint that fixes only safe P1/P2 items with minimal viable changes. Validate release stage and gate verdicts, generate an approved rollback plan, and execute fixes with targeted QA verification.

What is the best way to scope bugs for a day-one patch without scope creep?▼

Scoping bugs for a day-one patch requires filtering issues by severity, priority, and estimated effort, typically under four hours. Avoid new features or refactoring, explicitly defer unsuitable items, and focus only on safe P1/P2 fixes to prevent scope creep.

Do I need a rollback plan before implementing a day-one patch?▼

A rollback plan is mandatory before day-one patch implementation begins. You must produce and write the rollback plan, including platform constraints and rollback triggers, ensuring governance and safe recovery before any code changes ship.

How do I verify release readiness before shipping a day-one patch?▼

Verify release readiness by confirming the project is in the correct Release or Polish stage. Check gate verdicts, open and verified bug status, sprint context, and security audit notes to ensure all build gating criteria are met before patching.

What limitations exist when fixing bugs in a day-one patch?▼

Limitations of a day-one patch include fixing only safe P1/P2 items with minimal viable changes and avoiding any new features or refactoring. Unsuitable or complex issues must be explicitly deferred rather than rushed into the launch patch.

Can I generate player-facing patch notes after a day-one patch?▼

Generating player-facing patch notes is supported after completing the day-one patch. The process produces an internal patch record written to production releases, which then enables creation of external patch notes and bug closure workflows.

Related Skills

Explore More Software Engineering Skills→
nuoyanruoshuinuoyanruoshui
47

day-one-patch

Coordinate safe bug fixes for day-one game launch patches with QA validation and rollback planning.

Community
Advanced
CarlosQ96CarlosQ96

patch-notes

Generate categorized player-facing patch notes from git history and changelogs.

Community
Advanced
gethamstergethamster
7

qa

Automate QA testing across diff-aware, regression, and smoke modes.

Official
Advanced
CarlosQ96CarlosQ96

day-one-patch

Scope, implement, and QA-gate fixes for a game's day-one patch.

Community
Advanced