hotfix

Port provenance: adapted from the pinned upstream source at 984023ddac0d5e27624f2baacde6105e45de375f under MIT; see the repository parity ledger for the exact path and blob.

Explicit invocation only: This skill should only run when the user explicitly requests it with $ai-game-studio:hotfix. Do not auto-invoke based on context matching.

Phase 1: Assess Severity

Read the bug description or ID. Assess severity using these criteria:

• S1 (Critical): Game unplayable, data loss, security vulnerability
• S2 (Major): Significant feature broken, workaround exists
• S3 or lower: Minor issue — normal bug fix workflow applies

Confirm with the available user-input mechanism:

• Prompt: "I've assessed this as [assessed severity] — [brief rationale]. Confirm severity to proceed:"
• Options:
  • [A] S1 (Critical) — game unplayable, data loss, or security issue
  • [B] S2 (Major) — significant feature broken, workaround exists
  • [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:

## 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:

Shell example (adapt syntax to the current platform): git rev-parse --is-inside-work-tree 2>/dev/null