agentleFS
Sign inStart free
tejastn10tejastn10/workbench/skills/deployment/hotfix/SKILL.md

hotfix

Skill1 starsChanged 2 months agoMITView on GitHub

Ship an urgent production fix without the full process overhead but without cutting the dangerous corners — smallest possible change, branch from the released tag, cherry-pick, expedited review, deploy with extra watching, then backport to main. Use when prod is broken or degraded and the normal release cadence is too slow.

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

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Smallest change that stops the bleeding: Not the "proper" fix, not a refactor, not "while I'm in here".

    line 13
  2. Very specific:

    If you can mitigate without code (flag off, config, scale up, rate-limit the bad path) — do that first (deployment/rollback), it's faster …

    line 15
  3. Distinctive:

    Run CI (tests, security-audit).

    line 31

“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

Hotfix

The goal: minimum change, minimum delay, without skipping the checks that stop the hotfix from making things worse.

Scope

  • Smallest change that stops the bleeding. Not the "proper" fix, not a refactor, not "while I'm in here". One concern.
  • If you can mitigate without code (flag off, config, scale up, rate-limit the bad path) — do that first (deployment/rollback), it's faster and safer.

Branch & build

  • Branch from the currently released tag, not from main (main may have unreleased changes you don't want in prod). git checkout -b bugfix/<slug> <last-release-tag>.
  • Make the fix. Add a regression test — even under pressure, the test is what stops the recurrence and proves the fix.
  • Conventional commit: fix: <what>.

Review & ship

  • Still reviewed — a second pair of eyes, expedited. A blocking-only review (../pr-review/): does it fix the thing, does it break anything, is it minimal.
  • Run CI (tests, security-audit). Don't skip it — a hotfix that fails a test is not a hotfix.
  • Deploy with the canary + watch from deployment/deploy-service, and watch longer than usual.
  • Tag it — a patch release (deployment/cut-release): a fix: since the last tag → patch bump vX.Y.Z+1.

After

  • Backport to main immediately (cherry-pick or a forward PR) so the next release doesn't regress the fix.
  • Postmortem (incident/postmortem) — the hotfix bought time; the real fix and prevention still need to happen.

Anti-patterns

  • ❌ Branching from main and dragging unreleased changes into prod.
  • ❌ Skipping review or CI "because it's urgent".
  • ❌ No regression test.
  • ❌ Bundling the "real" fix or cleanup into the hotfix.
  • ❌ Forgetting to backport → next release reintroduces the bug.

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