agentleFS
Sign inStart free
edjchapmanedjchapman/claude-code-config/skills/hotfix/SKILL.md

hotfix

Skill8 starsChanged 19 days agoMITView on GitHub

Ship an urgent production fix — minimal change, targeted tests, PR. Use when the user says "hotfix" or describes a bug that has to reach main now.

  • Commits and pushes

29 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 10 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-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 14 projects that use this

  • +5 more from lilangMax
  • +3 more from CoralGame

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 6

    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:

    Ask the user to confirm the branch name before creating it.

    line 25
  2. Distinctive:

    Do NOT refactor surrounding code

    line 36
  3. Distinctive:

    Do NOT add features or improvements

    line 37
  4. Distinctive:

    Add a targeted test that reproduces the bug and verifies the fix

    line 38
  5. Distinctive:

    Run only the tests directly related to the fix:

    line 42
  6. Distinctive:

    Consider if a follow-up ticket is needed for deeper investigation

    line 77

“Common” is measured: kept by at least 6 in 10 of the 27 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

Guide me through creating a hotfix: branch from main, apply a minimal fix, run targeted tests, and prepare a PR.

Arguments

$ARGUMENTS

  • Describe the bug or issue that needs an urgent fix
  • Example: /hotfix users getting 500 on password reset

Steps

1. Create Hotfix Branch

git fetch origin main
git checkout -b hotfix/<short-description> origin/main

Ask the user to confirm the branch name before creating it.

2. Investigate the Issue

  • Locate the relevant code based on the bug description
  • Identify the root cause with minimal investigation
  • Focus on the immediate fix, not broader refactoring

3. Apply Minimal Fix

  • Make the smallest possible change that resolves the issue
  • Do NOT refactor surrounding code
  • Do NOT add features or improvements
  • Add a targeted test that reproduces the bug and verifies the fix

4. Verify

Run only the tests directly related to the fix:

  • Django: python3 manage.py test <app.tests.TestClass> --no-input
  • TypeScript: npx vitest run <specific_test_file>
  • Full suite: python3 manage.py test --no-input --parallel=8 (if fast enough)

5. Prepare PR

Use gh pr create with:

  • Title: hotfix: <description>
  • Label: hotfix (if available)
  • Body should include:
    • Problem: What was broken
    • Root Cause: Why it happened
    • Fix: What was changed and why
    • Risk: Assessment of the fix's impact
    • Test Plan: How the fix was verified

6. Post-Fix Checklist

Present to the user:

  • Fix is minimal and targeted
  • Test reproduces the original bug
  • Test passes with the fix
  • No unrelated changes included
  • PR description explains the urgency

Output

Present the PR URL when complete and remind the user to:

  • Request expedited review
  • Monitor deployment after merge
  • Consider if a follow-up ticket is needed for deeper investigation

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.

Check your setup, free