Skip to content

synesenom/ran / .claude/skills/hotfix

hotfix

Verified

Hotfix Skill

You are applying a small, targeted fix without the full research/plan/implement pipeline.

Core Principle

For trivial fixes (wrong constant, one-line formula correction, missing constraint), skip research and planning. Go straight to fix → test → review → ship.

When to Use

This skill is for changes that are:

  • Small: 1-10 lines of production code
  • Obvious: The fix is clear without research
  • Low-risk: No architectural decisions, no new abstractions

If the fix requires understanding complex mathematical interactions or touches more than ~3 files, use /build or the manual pipeline instead.

Workflow

When the user invokes /hotfix <description> or /hotfix #<issue>:

1. Understand the Fix

  • If a GitHub issue is referenced, fetch it: gh issue view <number> (or mcp__github__issue_read)
  • Parse the description from the user
  • Understand what needs to change and why

2. Create a Branch

git checkout main && git pull

If an issue number is given:

gh issue develop <number> --name <number>-<slug> --checkout

gh unavailable: git checkout -b <number>-<slug>

If no issue number is given: git checkout -b <slug>

3. Find the Code

  • Use Glob and Grep to locate the relevant code
  • Read the affected files

4. Apply the Fix (TDD)

a. Write/update tests first — write a test for the expected correct behavior b. Verify the test fails:

npm test

c. Apply the fix — make the minimal change d. Run linting and tests:

npm run standard
npm test

e. If tests fail: debug directly — no recovery agents needed for a small fix

5. Bug Triage

Compile observations noticed during step 4 (a flaky test, a pre-existing NaN at a boundary, a contradicting docstring, etc.) into a structured list with summary, stage, evidence, and your tentative orchestrator_call.

Spawn the ops-triage agent with branch, session_kind: "hotfix", target_issue, the observations list, and a diff_path (run git fetch origin main && git diff origin/main...HEAD > .claude/tmp/triage-diff-<branch>.patch first — diffing against a freshly-fetched origin/main avoids a stale local main ref when the session started already checked out on the feature branch, so step 2 never touched local main).

Act on the result:

  • definite with route: "fix" (trivial/moderate): spawn the ops-fix agent with summary, difficulty, fix_context, and branch, one bug at a time (sequentially — they share the working tree). On status: "fixed", count as "fixed inline". On status: "escalated", fall back to ops-issue using the entry's drafted title/priority/extra_labels and a body built from summary + the escalation reason.
  • definite with route: "file" (difficult): invoke ops-issue once per entry with the drafted fields. Collect URLs.
  • ambiguous: one batched AskUserQuestion (File issue / Skip / Other). For each "File issue", invoke ops-issue.
  • not_a_bug: silent.

Report: > "Triage: <N> fixed inline, <M> filed (<URLs>), <K> skipped, <L> not a bug." or > "Triage: clean."

6. Review + Auto-fix

Invoke /review via the Skill tool.

If P1/P2 findings: auto-fix, re-run tests, then re-invoke /review once.

  • If the second review still has P1/P2 findings: STOP and report.
  • If P3 only or no findings: proceed to commit.

7. Ship (fully autonomous)

Invoke all three sub-skills in sequence without any pause or output between them. As soon as one returns, invoke the next immediately. Do not generate any text between steps — no "committing now", no "pushing...", no confirmation prompts. Proceed directly to step 8 only after all three have completed.

a. Commit — invoke /commit b. Push — invoke /push immediately after /commit returns c. Pull Request — invoke /pr immediately after /push returns

8. Report

"Hotfix applied: <commit hash>

Changed: Tests: All passing Triage: filed / skipped / clean Review: PASSED PR: "

Rules

DO:

  • Keep it small — if the fix grows beyond ~10 lines, stop and suggest /build
  • Write tests for behavior changes
  • Run the full test suite before committing

DO NOT:

  • Create research documents, plans, or progress files
  • Refactor surrounding code
  • Skip creating a branch — always branch from main
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 193kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 193kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 193kUpdated Claude CodeCodexVerifiedInstall