hotfix
Skill9 starsChanged 7 months agoMITView on GitHub
Emergency fix workflow — diagnose, apply minimal fix, test, publish, and post-mortem. Use when a live issue requires immediate action.
30 other projects use a version of this.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- cyrilichti/agent-workflowstheir own version, first seen Nov 8, 2026
- jacksnxly/keryxtheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- florian101010/awesome-agentic-AI-coding-templatetheir own version, first seen Nov 1, 2026
Used with
Projects with it also use playtest-report, soak-test and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 12 projects that use this
- +5 more from lilangMax
- +2 more from CoralGame
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- microsoft/roosterjs★ 1.3ksame name
- nudgebee/nudgebee★ 525same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- tranhieutt/software_development_department★ 71same name
- Aurealibe/claude-config★ 68same name
- cenconq25/claude-code-app-studio★ 40same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dawn840705/codex-code-studios★ 17same name
20 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
If answer to "can this wait" is "yes" → not a hotfix.
- Distinctive: line 43
Targeted: Only touch files related to the bug
- Distinctive: line 45
Tested: Verify it fixes the issue without breaking neighbors
- Distinctive: line 55
Test neighboring functionality → verify no regression
- Distinctive: line 56
Test common user flows → verify no side effects
- Distinctive: line 57
If possible, test in a private place first
- Distinctive: line 62
If diff is < 20 lines, review should be < 10 minutes
- Distinctive: line 66
Use feature flag to enable fix if possible (instant rollback path)
- Distinctive: line 71
Verify fix is working for affected users
- Distinctive: line 75
Every hotfix gets a post-mortem.
- Distinctive: line 77
When it broke: When did this start affecting users?
- Distinctive: line 82
Timeline: When it was detected → fixed → published
“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/hotfix — Emergency Fix Workflow
Delegate to: release-manager (with technical-director, relevant specialist for actual fix)
When to Use
- Live game broken for many users
- Critical security exploit discovered
- Data loss occurring
- Monetization broken
- Any issue that warrants interrupting normal sprint work
DO NOT Use For
- Minor bugs (use normal bug process)
- Features that didn't make the last release
- Polish items
Steps
1. Triage — Is This a Hotfix?
Confirm:
- Severity: Is this truly S0 or S1?
- Impact: How many users affected?
- Urgency: Can this wait for next scheduled release?
- Workaround: Is there a temporary workaround players can use?
If answer to "can this wait" is "yes" → not a hotfix. Use normal process.
2. Diagnose Fast
- Reproduce the issue (fast repro is critical)
- Identify root cause (not just symptom)
- Identify affected files/systems
- Delegate to the most relevant specialist for root-cause analysis
3. Design Minimal Fix
The fix should be:
- Minimal: Smallest possible change to fix the issue
- Targeted: Only touch files related to the bug
- Reversible: Easy to revert if the fix causes new issues
- Tested: Verify it fixes the issue without breaking neighbors
DO NOT:
- Bundle unrelated improvements
- Refactor around the bug
- Add new features
- Make "while we're here" changes
4. Test the Fix
- Reproduce the original issue → verify fix works
- Test neighboring functionality → verify no regression
- Test common user flows → verify no side effects
- If possible, test in a private place first
5. Expedited Review
- Quick code review (via lead-programmer or technical-director)
- Minimum checks: no hardcoded values, no client-trust, no new security holes
- If diff is < 20 lines, review should be < 10 minutes
6. Publish
- Publish directly to production place (skip staging if urgent)
- Use feature flag to enable fix if possible (instant rollback path)
- Communicate immediately via community channels
7. Monitor
- Watch metrics for 1-2 hours post-publish
- Verify fix is working for affected users
- Watch for new issues introduced by the fix
8. Post-Mortem (within 48 hours)
Every hotfix gets a post-mortem. Document:
- What broke: Clear description of the issue
- When it broke: When did this start affecting users?
- How it was detected: Player reports / monitoring / internal
- Root cause: Why did this happen?
- Fix: What was changed
- Prevention: What process change would prevent this in the future?
- Timeline: When it was detected → fixed → published
Save to production/incidents/hotfix-<date>-<summary>.md.
Output — Hotfix Report
# Hotfix: [Short description]
**Severity**: [S0/S1]
**Reported**: YYYY-MM-DD HH:MM
**Detected By**: [source]
**Fixed**: YYYY-MM-DD HH:MM
**Deployed**: YYYY-MM-DD HH:MM
**Duration of Impact**: X hours
## The Issue
[1-2 sentences on what broke]
## Root Cause
[1 paragraph on why]
## The Fix
- Files changed:
- [file 1]: [what changed]
- Lines changed: N
- Review: [who reviewed]
- Tests: [what was tested]
## Verification
- [How we verified the fix worked]
## Prevention
- [What to do to prevent this class of issue in the future]
## Action Items
- [ ] [Follow-up action]
- [ ] [Follow-up action]Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

