Skip to content

synesenom/ran / .claude/skills/fix

Fix Skill

You are fixing a straightforward GitHub issue that does not require research or planning — just do the work and ship it.

Core Principle

For issues where the fix is obvious (docs updates, formula corrections, parameter constraint additions, small refactors), skip the research/plan pipeline entirely. Go straight to branch → fix → test → ship.

When to Use

This skill is for issues that are:

  • Self-explanatory: The issue description tells you exactly what to do
  • No design decisions: No architectural choices, no alternatives to weigh
  • Any size: Unlike /hotfix (which caps at ~10 lines), this handles larger changes that don't need research or planning

If the issue requires understanding complex mathematical interactions or making design decisions, use /build instead.

Workflow

When the user invokes /fix <argument>:

1. Fetch the Issue

gh issue view <number>

(or mcp__github__issue_read if gh is unavailable)

2. Create a Branch

git checkout main && git pull
gh issue develop <number> --name <number>-<slug> --checkout

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

3. Do the Work

  • Use Glob and Grep to locate relevant files
  • Read the files to understand the current state
  • Make all the changes needed to resolve the issue
  • Make independent edits in parallel where possible

4. Run Tests

npm run standard
npm test

If tests fail, debug and fix. If the fix grows too complex, stop and suggest /build instead.

5. Bug Triage

Compile observations noticed during steps 3–4 (pre-existing NaN at a boundary, a flaky test, a docstring that contradicts the code, etc.) into a structured list. Each entry needs summary, stage, evidence, and your tentative orchestrator_call.

Spawn the ops-triage agent with branch, session_kind: "fix", 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 if not already done — diffing against a freshly-fetched origin/main avoids a stale local main ref when the session started already checked out on the feature branch).

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 (conditional)

Check if any .js files were modified:

git fetch origin main && git diff origin/main --name-only | grep '\.js$'

If .js files were modified: invoke /review via the Skill tool. If P1/P2 findings, auto-fix, re-run tests, and re-review once. If still P1/P2 after retry, STOP and report.

If no .js files were modified: skip review.

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 confirmation prompts, no interim status messages. 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

"Resolved: <commit hash>

Issue: # — Changed: Tests: All passing Triage: filed / skipped / clean Review: PASSED / SKIPPED (no .js changes) PR: "

Rules

DO:

  • Always start from a clean main
  • Run the full test suite before shipping
  • Review when .js files are touched

DO NOT:

  • Create research documents, plans, or progress files
  • Refactor surrounding code — only resolve the issue
  • Continue if the work becomes complex enough to need planning — suggest /build instead
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