# Hotfix

Emergency fix bypassing normal sprint process, hotfix branch, approvals tracked...

- Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (32144 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-19
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Donchitos/Claude-Code-Game-Studios --skill hotfix -g -a claude-code -y`
Codex: `npx skills add Donchitos/Claude-Code-Game-Studios --skill hotfix -g -a codex -y`
Cursor: `npx skills add Donchitos/Claude-Code-Game-Studios --skill hotfix -g -a cursor -y`
Gemini CLI: `npx skills add Donchitos/Claude-Code-Game-Studios --skill hotfix -g -a gemini-cli -y`

## Description

Emergency fix bypassing normal sprint process, hotfix branch, approvals tracked, backport verified, full audit trail.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Hotfix

> **Explicit invocation only**: This skill should only run when the user explicitly requests it with `/hotfix`. Do not auto-invoke based on context matching.

## Phase 1: Assess Severity

Read the bug description or ID. Assess severity on `/bug-triage`'s scale:

- **S1 (Critical)**: Crash, data loss, or complete feature failure, the game cannot proceed (rate a security issue by that impact)
- **S2 (High)**: Major feature broken, but the game is still playable
- **S3 or lower**: Feature degraded with a workaround, or cosmetic, normal bug fix workflow applies

Confirm with `AskUserQuestion`:
- Prompt: "I've assessed this as **[assessed severity]**, [brief rationale]. Confirm severity to proceed:"
- Options:
  - `[A] S1 (Critical), crash, data loss, or complete feature failure`
  - `[B] S2 (High), major feature broken, game still playable`
  - `[C] S3 or lower, redirect to normal bug fix workflow`

If [C]: stop. Verdict: **REDIRECTED**, use the normal bug fix workflow for S3 and below.

---

## Phase 2: Create Hotfix Record

Draft the hotfix record:

```markdown
## Hotfix: [Short Description]
Date: [Date]
Severity: [S1/S2]
Reporter: [Who found it]
Status: IN PROGRESS

### Problem
[Clear description of what is broken and the player impact]

### Root Cause
[To be filled during investigation]

### Fix
[To be filled during implementation]

### Testing
[What was tested and how]

### Approvals
- [ ] Fix reviewed by lead-programmer
- [ ] Regression test passed (qa-tester)
- [ ] Release approved (producer)

### Rollback Plan
[How to revert if the fix causes new issues]
```

Ask: "May I write this to `production/hotfixes/hotfix-[date]-[short-name].md`?"

If yes, write the file, creating the directory if needed.

---

## Phase 3: Create Hotfix Branch

Check whether this is a git repository:

`Bash: git rev-parse --is-inside-work-tree 2>/dev/null`

The rest: https://github.com/Donchitos/Claude-Code-Game-Studios/blob/HEAD/.claude/skills/hotfix/SKILL.md