New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Debug Fix

by poshan0126 in poshan0126/dotclaude

Find and fix a bug. An agent skill from poshan0126/dotclaude.

MITAuto-check passedDevelopment

Install Debug Fix

skills CLI
$ npx skills add poshan0126/dotclaude --skill debug-fix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install poshan0126/dotclaude debug-fix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/poshan0126/dotclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/debug-fix .claude/skills/debug-fix && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
debug-fix
GitHub stars
871
Token cost
~1.2k tokens
SKILL.md length
667 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Find and fix a bug. An agent skill from poshan0126/dotclaude.

  • Works in 7 steps: Understand → Hotfix branch (--fast only) → Reproduce (default only) → …
  • Development work in your project
  • SKILL.md covers Mode, Step 1: Understand, Step 2: Hotfix branch (--fast… and Step 3: Reproduce (default only), plus 5 more sections
  • Calls git and gh

What it does

Debug Fix is an agent skill from poshan0126/dotclaude. Find and fix a bug. Default is careful (reproduce, investigate, test). Add --fast for emergency production mode (hotfix branch, minimal change, ship a PR fast).

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Git. The repository describes itself as: The standard .claude/ folder structure for everyday development. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/debug-fix”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git *), Bash(gh *), Bash(npm run test *), Bash(npm run build), Read, Glob, Grep, Edit, Write

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Understand
  2. Hotfix branch (--fast only)
  3. Reproduce (default only)
  4. Investigate (default only)
  5. Fix
  6. Verify
  7. Wrap up or ship

What it can do on your machine

Read from SKILL.md and the folder at commit 94b84b9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git *)
    • Bash(gh *)
    • Bash(npm run test *)
    • Bash(npm run build)
    • Read
    • Glob
    • Grep
    • Edit
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debug Fix loads about 1.2k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 667 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from poshan0126/dotclaude at commit 94b84b9, republished under its MIT licence (© poshan0126). 667 words, ~1,222 tokens.

Download SKILL.mdSave it as .claude/skills/debug-fix/SKILL.md (or your agent's skills folder).
name
debug-fix
description
Find and fix a bug. Default is careful (reproduce, investigate, test). Add `--fast` for emergency production mode (hotfix branch, minimal change, ship a PR fast).
allowed-tools
Bash(git *), Bash(gh *), Bash(npm run test *), Bash(npm run build), Read, Glob, Grep, Edit, Write
argument-hint
[issue, error, or description] [optional: --fast]
disable-model-invocation
true

Find and fix the following issue:

Problem: $ARGUMENTS

Mode

Check $ARGUMENTS for --fast. Strip it before parsing the problem description.

  • Default: careful debug-fix. Use when you have time to do this right.
  • --fast: emergency hotfix. Use when production is broken and shipping speed matters more than thoroughness. Triggers a hotfix/* branch from production, minimal-change discipline, critical-tests-only verification, and ships a [HOTFIX] PR. Before committing to fast mode, briefly confirm with the user that this is genuinely emergency-grade. If not, suggest dropping --fast.

Step 1: Understand

  • Issue number: gh issue view $ARGUMENTS (or the project's issue tracker).
  • Error or stack trace: parse it for file, line, error type, and call chain.
  • Description: identify expected vs actual.
  • URL or screenshot: examine the referenced resource.

If unclear, ask clarifying questions before proceeding.

Step 2: Hotfix branch (--fast only)

In --fast mode only:

  • Detect the production branch: git symbolic-ref refs/remotes/origin/HEAD or git remote show origin.
  • Stash uncommitted work if needed.
  • Create and switch to hotfix/<short-description> branched from production.
  • ASK the user to confirm the branch name first.

In default mode, skip this. Branch creation happens in Step 7.

Step 3: Reproduce (default only)

In --fast mode, skip this step. Trust the report and move to Step 5.

  • Find the simplest way to trigger the issue (a test, curl, script).
  • Confirm you can reproduce reliably.
  • If you can't reproduce:
    • Environment-specific? Check env vars, OS, runtime version, database state.
    • Intermittent? Likely a race condition. Look for shared mutable state, timing dependencies, async ordering assumptions.
    • Already fixed? git log for recent commits mentioning the issue.

Step 4: Investigate (default only)

In --fast mode, skip this and go to Step 5. Trust the report and minimize investigation depth.

Don't skip ahead to guessing:

  1. Locate the symptom. Which file and line produces the wrong output?
  2. Read the code path backwards. What called this? What data was passed?
  3. Check git history: git log --oneline -20 -- <file>, git log --all --grep="<keyword>".
  4. Narrow scope with git bisect or targeted grep.
  5. Form a hypothesis: "X is wrong because Y."
  6. Verify the hypothesis with a targeted log or assertion.
  7. If wrong, trace a different path. Don't keep guessing the same hypothesis.
Show full SKILL.md (303 more words)Show less

Step 5: Fix

  • Make the smallest correct change.
  • Don't patch symptoms. Trace back to where bad data originates and fix it there.
  • Don't refactor surrounding code while fixing.
  • Don't add defensive checks that mask the problem.

In --fast mode specifically:

  • If the fix needs more than ~50 lines changed, warn the user. This may not actually be a hotfix.
  • Do NOT add features, change formatting, clean up unrelated issues, or add non-essential comments.

Step 6: Verify

Default:

  • Write a test that reproduces the bug and now passes.
  • Run related tests for regressions.
  • Run lint and typecheck.
  • Temporarily revert your fix and confirm the new test fails (proves the test catches the bug).

--fast:

  • Run only tests directly relevant to the changed code, not the full suite.
  • Run the build.
  • If you can reproduce the original error, verify it's fixed.
  • ASK the user if they want extra verification before shipping.

Step 7: Wrap up or ship

Default:

  • Create a branch if not already on one.
  • Stage only the fix and test files.
  • Commit: fix: <what was wrong and why> (#number).

--fast:

  • Stage only the fix files (never secrets, locks, or build output).
  • Draft commit: hotfix: <short description>. ASK the user to confirm.
  • Push: git push -u origin hotfix/<description>.
  • Create a PR targeting production:
    • Title: [HOTFIX] <description>.
    • Body: what broke, what caused it, what this fixes.
    • Try to add the hotfix label: gh pr create ... --label hotfix. Fall back to no label on failure.
  • Show the PR URL.

Rules

  • NEVER skip confirmation steps in --fast mode (branch name, commit message, push).
  • NEVER force-push.
  • NEVER commit secrets or unrelated changes.
  • If the user says "skip" at any step, skip and move on.
  • In --fast mode specifically: if the fix turns out to be complex, tell the user and suggest dropping --fast to use the careful path.

© poshan0126, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/debug-fix of poshan0126/dotclaude.

Open the folder on GitHubat commit 94b84b9

Compare with similar skills

Debug Fix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debug Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debug Fix this skillposhan0126/dotclaude871—~1.2kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything85k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    85k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    85k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from poshan0126/dotclaude

All 14 skills in this repo

  • Session Catchup and Handoff

    poshan0126/dotclaude

    Rebuilds working context after /clear by reading a handoff note and the branch's git state, or writes that handoff note before a session ends.

    871 GitHub stars~811 tokensUpdated 1 mo ago
    Auto-check passed

  • Context Budget Check

    poshan0126/dotclaude

    Estimates the per-turn token cost of a project's .claude folder and CLAUDE.md, split into always-loaded, path-scoped and invoked-only files, and flags what runs over budget.

    871 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Codebase Onboarding Tour

    poshan0126/dotclaude

    Builds a quick mental model of an unfamiliar codebase by dispatching read-only Explore subagents and merging their findings into one brief.

    871 GitHub stars~858 tokensUpdated 1 mo ago
    Auto-check passed

  • Parallel Specialist PR Review

    poshan0126/dotclaude

    Reviews a pull request, staged changes or a file by sending the diff to specialist reviewer agents in parallel, then merges their findings into one compact report.

    871 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • dotclaude Project Setup

    poshan0126/dotclaude

    Scans a codebase, interviews you, and installs only the justified Claude Code rules, hooks, agents and skills, tailored to the project's stack.

    871 GitHub stars~3.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Ship Changes

    poshan0126/dotclaude

    Walks through commit, push and pull request creation for the current changes, asking you to confirm the files, message, push and PR text at each step.

    871 GitHub stars~953 tokensUpdated 1 mo ago
    Auto-check: notes

Works with

Categories

Questions about Debug Fix

What does Debug Fix do?

Find and fix a bug. An agent skill from poshan0126/dotclaude. Debug Fix is an agent skill from poshan0126/dotclaude. Find and fix a bug.

When should I use Debug Fix?

Debug Fix fits situations like: development work in your project.

How do I install Debug Fix in Claude Code?

Run `npx skills add poshan0126/dotclaude --skill debug-fix -a claude-code`. Or copy the skill folder (skills/debug-fix in poshan0126/dotclaude) into .claude/skills/debug-fix in your project. Claude Code loads it when a task matches its description.

How do I install Debug Fix in Codex?

Run `npx skills add poshan0126/dotclaude --skill debug-fix -a codex`. Or copy the skill folder (skills/debug-fix in poshan0126/dotclaude) into .agents/skills/debug-fix in your project. Codex loads it when a task matches its description.

Can I use Debug Fix in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add poshan0126/dotclaude --skill debug-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-fix, .gemini/skills/debug-fix, .github/skills/debug-fix and .opencode/skills/debug-fix in your project.

What does Debug Fix need to run?

Going by SKILL.md and its folder, Debug Fix needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash(git *), Bash(gh *), Bash(npm run test *), Bash(npm run build), Read, Glob, Grep, Edit, Write.

Does Debug Fix access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Debug Fix safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Debug Fix use?

Debug Fix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Debug Fix use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Debug Fix?

Skills that share tags, products or a category with Debug Fix: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug Fix?

poshan0126 (a GitHub user) maintains it in poshan0126/dotclaude, which has 871 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on August 27, 2026.

Source: poshan0126/dotclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.