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. Determine severity: - **S1 (Critical)**: Game unplayable, data loss, security vulnerability — hotfix immediately - **S2 (Major)**: Significant feature broken, workaround exists — hotfix within 24 hours - If severity is S3 or lower, recommend using the normal bug fix workflow instead and stop. --- ## 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 If git is initialized, create the hotfix branch: ``` git checkout -b hotfix/[short-name] [release-tag-or-main] ``` --- ## Phase 4: Investigate and Implement Focus on the minimal change that resolves the issue. ...