agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/hotfix/SKILL.md

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

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.
  • CoralGameSkill

    playtest-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

  • lilangMaxSkill

    soak-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

  • lilangMaxSkill

    team-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

  • CoralGameSkill

    team-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

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
  1. Distinctive:

    If answer to "can this wait" is "yes" → not a hotfix.

    line 32
  2. Distinctive:

    Targeted: Only touch files related to the bug

    line 43
  3. Distinctive:

    Tested: Verify it fixes the issue without breaking neighbors

    line 45
  4. Distinctive:

    Test neighboring functionality → verify no regression

    line 55
  5. Distinctive:

    Test common user flows → verify no side effects

    line 56
  6. Distinctive:

    If possible, test in a private place first

    line 57
  7. Distinctive:

    If diff is < 20 lines, review should be < 10 minutes

    line 62
  8. Distinctive:

    Use feature flag to enable fix if possible (instant rollback path)

    line 66
  9. Distinctive:

    Verify fix is working for affected users

    line 71
  10. Distinctive:

    Every hotfix gets a post-mortem.

    line 75
  11. Distinctive:

    When it broke: When did this start affecting users?

    line 77
  12. Distinctive:

    Timeline: When it was detected → fixed → published

    line 82

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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]

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.