hotfix

Orchestrates emergency game fixes with severity assessment, approvals, QA gates, and rollback plans.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill hotfix-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/hotfix
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill hotfix-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Critical bugs in a shipped game cannot wait for the normal sprint cycle, but rushing a fix without process risks breaking something else. This Skill provides a controlled emergency fix workflow with a full audit trail, so S1 and S2 issues get resolved fast without skipping review, testing, or rollback planning. ## Core Features & Use Cases - Severity Triage: Classifies bugs as S1 (critical), S2 (major), or S3 (redirect to normal bug workflow) with user confirmation before proceeding. - Audited Hotfix Lifecycle: Creates a hotfix record file, a dedicated git branch, and collects parallel sign-offs from lead-programmer, qa-tester, and producer subagents. - QA Re-Entry Gate: Determines whether a smoke check, targeted team-qa pass, or full QA sprint is required before deployment. - Use Case: A live game has a save-data corruption bug. Invoke the hotfix workflow to assess it as S1, create a hotfix branch, implement the minimal fix, gather three approvals, pass the QA gate, and deploy with a documented rollback plan. ## Quick Start Use $ai-game-studio:hotfix to run the emergency fix workflow for the reported save corruption bug and produce a deployment-ready hotfix record.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I run an emergency hotfix workflow for a live game bug?

Invoke the hotfix skill explicitly with the bug description or ID. It assesses severity, creates a hotfix record and branch, implements the minimal fix, collects three approvals, passes a QA gate, and outputs a deployment summary with rollback plan.

What severity levels does a game hotfix process use?

The workflow uses S1 for critical issues like unplayable games, data loss, or security vulnerabilities, and S2 for major broken features with workarounds. S3 or lower issues are redirected to the normal bug fix workflow.

Does the hotfix workflow work without a git repository?

Yes. The workflow checks whether the project is inside a git work tree first. If the check fails, it notes that no repository exists, skips branch creation, and continues with the hotfix record and approval phases.

Who must approve a game hotfix before deployment?

Three subagent roles must all return APPROVE: lead-programmer reviews correctness and side effects, qa-tester runs targeted regression tests, and producer approves deployment timing and communication. Any CONCERNS or REJECT blocks deployment.

When should I not use the hotfix workflow?

Do not use it for S3 or lower severity bugs, which belong in the normal bug fix workflow. Also escalate to the technical-director instead if the fix is complex enough to require more than four hours of work.