Agent skill

Debugger

Systematic debugging methodology for diagnosing failures and root cause analysis.

MITAuto-check passedDevelopment

Install Debugger

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill debugger -a claude-code

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

GitHub CLI

$ gh skill install TechDufus/oh-my-claude debugger --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/TechDufus/oh-my-claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/oh-my-claude/skills/debugger .claude/skills/debugger && 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/

Paste into Claude Code

Install the "debugger" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/debugger into .claude/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/debugger

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill debugger -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude debugger --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/oh-my-claude/skills/debugger .agents/skills/debugger && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "debugger" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/debugger into .agents/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill debugger -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude debugger --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/oh-my-claude/skills/debugger .cursor/skills/debugger && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "debugger" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/debugger into .cursor/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/TechDufus/oh-my-claude.git --path plugins/oh-my-claude/skills/debugger

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill debugger -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude debugger --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/oh-my-claude/skills/debugger .gemini/skills/debugger && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "debugger" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/debugger into .gemini/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude debugger

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill debugger -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/oh-my-claude/skills/debugger .github/skills/debugger && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "debugger" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/debugger into .github/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill debugger -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude debugger --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/oh-my-claude/skills/debugger .opencode/skills/debugger && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "debugger" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/debugger into .opencode/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: debugger
GitHub stars: 174
Token cost: ~1k tokens
SKILL.md length: 404 words
Files: 1
Skills in repo: 12
Repo updated: Jul 13, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Systematic debugging methodology for diagnosing failures and root cause analysis.

Works in 3 steps: Restate the Problem → Generate Ranked Hypotheses → Systematic Verification
: 2+ failed fix attempts
SKILL.md covers When to Apply This Guidance, Structured Analysis Framework, Reasoning Principles and Decision Framework, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Debugger is an agent skill from TechDufus/oh-my-claude. Systematic debugging methodology for diagnosing failures and root cause analysis. Triggers on: 2+ failed fix attempts, 'ultradebug', 'uld', debugging in circles, complex system failures, intermittent bugs.

Its SKILL.md is about 1k 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, covering Debugging and Root cause analysis. The repository describes itself as: Add ultrawork to any prompt for maximum parallel execution. The licence is MIT.

When your agent uses it

: 2+ failed fix attempts
Debugging in circles
Complex system failures
Intermittent bugs

Example prompts

“ultradebug”
“/debugger”

Workflow steps

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

Restate the Problem
Generate Ranked Hypotheses
Systematic Verification

What it can do on your machine

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

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Debugger loads about 1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 404 words of instructions outside code blocks.

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

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 TechDufus/oh-my-claude at commit ede75db, republished under its MIT licence (© TechDufus). 404 words, ~1,019 tokens.

Download SKILL.mdSave it as .claude/skills/debugger/SKILL.md (or your agent's skills folder).

name: debugger
description: Systematic debugging methodology for diagnosing failures and root cause analysis. Triggers on: 2+ failed fix attempts, 'ultradebug', 'uld', debugging in circles, complex system failures, intermittent bugs.

Debugger Skill

Systematic debugging methodology for diagnosing failures and root cause analysis.

When to Apply This Guidance

2+ failed fix attempts on the same issue
Debugging that's gone in circles
Complex system behavior you don't understand
Multi-system integration problems
Intermittent failures (Heisenbugs)

Structured Analysis Framework

Step 1: Restate the Problem

Before investigating, articulate:

What is the actual vs expected behavior?
What assumptions might be wrong?
What could cause the specific symptoms described?
Are there hidden dependencies or side effects?

Step 2: Generate Ranked Hypotheses

Always generate multiple hypotheses, ranked by likelihood:

Most Likely:

Evidence: What supports this theory?
Test: How to verify quickly?

Possible:

Evidence: What partially supports this?
Test: How to confirm or eliminate?

Unlikely but worth checking:

Evidence: Limited, but possible
Test: Quick check to rule out

Step 3: Systematic Verification

Test hypotheses in order. For each:

State what you're testing
Describe the expected outcome if hypothesis is correct
Execute the test
Document actual results
Update hypothesis ranking based on findings

Reasoning Principles

Challenge assumptions - The "obvious" cause is often wrong after 2+ failures
Follow the data - What do logs/errors actually say vs what's assumed?
Consider timing - Race conditions, async issues, initialization order
Check boundaries - Module interfaces, API contracts, type conversions
Question the environment - Config, dependencies, network, state

Show full SKILL.md (184 more words)Show less

Decision Framework

When choosing between approaches:

Factor	Weight	Considerations
Correctness	Critical	Does it actually solve the problem?
Simplicity	High	Prefer boring solutions over clever ones
Leverage	High	Use existing patterns/libraries/code
Developer Experience	Medium	How hard is it to debug/maintain?
Performance	Low*	*Unless performance IS the problem

Effort Estimation

Tag recommendations by effort:

Tag	Meaning	Example
[Quick]	<30 min	Add logging, check config
[Short]	30min-2hr	Refactor function, add test
[Medium]	2hr-1day	New component, integration
[Large]	>1 day	Architecture change

Common Failure Patterns

Pattern	Signal	Investigation Focus
Fix-break cycle	Each fix causes new problem	Root cause analysis - treating symptoms not cause
Confusion	"I don't understand why X happens"	Add logging, trace execution path
Tradeoff paralysis	Multiple valid approaches	Use decision framework above
Integration hell	System A + B don't work together	Interface contracts, data formats
Heisenbug	Works sometimes, fails randomly	Timing, state, race conditions

Traps to Avoid

Premature fixing - Understand before changing
Single hypothesis - Always consider alternatives
Assuming correctness - Verify each component independently
Ignoring evidence - If data contradicts theory, update theory
Scope creep - Fix the bug, not everything around it

Output Template

When debugging, structure findings as:

## Problem Understanding
{Restate in own words. Challenge framing if wrong.}

## Hypotheses (Ranked)
1. Most Likely: {hypothesis} - Evidence: {support} - Test: {verification}
2. Possible: {hypothesis} - Evidence: {support} - Test: {verification}
3. Unlikely: {hypothesis} - Evidence: {limited} - Test: {quick check}

## Recommended Approach
{Specific next steps. Be prescriptive.}

## Traps to Avoid
{What NOT to do for this specific problem.}

Files

Just SKILL.md in plugins/oh-my-claude/skills/debugger of TechDufus/oh-my-claude.

Open the folder on GitHubat commit ede75db

Compare with similar skills

Debugger 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.

Debugger compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Debugger this skillTechDufus/oh-my-claude	174	—	~1k	Automated safety check: Pass	MIT	2 mo ago
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi	23k	—	~2.5k	Automated safety check: Notes	Apache-2.0	4 days ago
Bug Finder for daisyUIsaadeghi/daisyui	43k	—	~2.3k	Automated safety check: Pass	MIT	8 days ago
Root Cause Debugginggarrytan/gstack	136k	—	~1.4k	Automated safety check: Pass	MIT	today
Graph-Based Bug Tracingtirth8205/code-review-graph	32k	1 repos	~287	Automated safety check: Pass	MIT	yesterday
Systematic DebuggingChrisWiles/claude-code-showcase	6.1k	3 repos	~1.2k	Automated safety check: Pass	None	9 mo ago

Similar skills

OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
23k GitHub stars~2.5k tokensUpdated 4 days ago
DevelopmentAuto-check: notes
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
43k GitHub stars~2.3k tokensUpdated 8 days ago
DevelopmentAuto-check passed
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
136k GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
32k GitHub starsUsed in 1 repo~287 tokens
DevelopmentAuto-check passed
Systematic Debugging
ChrisWiles/claude-code-showcase
Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.
6.1k GitHub starsUsed in 3 repos~1.2k tokens
DevelopmentAuto-check passed
Debugging and Error Recovery
addyosmani/agent-skills
Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.
103k GitHub starsUsed in 1 repo~2.6k tokens
DevelopmentAuto-check passed

Questions about Debugger

What does Debugger do?

Systematic debugging methodology for diagnosing failures and root cause analysis. Debugger is an agent skill from TechDufus/oh-my-claude. Systematic debugging methodology for diagnosing failures and root cause analysis.

When should I use Debugger?

Debugger fits situations like: : 2+ failed fix attempts; debugging in circles; complex system failures; intermittent bugs.

How do I install Debugger in Claude Code?

Run `npx skills add TechDufus/oh-my-claude --skill debugger -a claude-code`. Or copy the skill folder (plugins/oh-my-claude/skills/debugger in TechDufus/oh-my-claude) into .claude/skills/debugger in your project. Claude Code loads it when a task matches its description.

How do I install Debugger in Codex?

Run `npx skills add TechDufus/oh-my-claude --skill debugger -a codex`. Or copy the skill folder (plugins/oh-my-claude/skills/debugger in TechDufus/oh-my-claude) into .agents/skills/debugger in your project. Codex loads it when a task matches its description.

Can I use Debugger 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 TechDufus/oh-my-claude --skill debugger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugger, .gemini/skills/debugger, .github/skills/debugger and .opencode/skills/debugger in your project.

What does Debugger need to run?

SKILL.md names no scripts, command-line tools or credentials: Debugger is instructions for the agent only.

Does Debugger access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Debugger 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 Debugger use?

Debugger 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 Debugger use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Debugger?

Skills that share tags, products or a category with Debugger: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Graph-Based Bug Tracing (tirth8205/code-review-graph, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debugger?

TechDufus (a GitHub user) maintains it in TechDufus/oh-my-claude, which has 174 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 13, 2026.

Source: TechDufus/oh-my-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Debugger

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Debugger Skill

When to Apply This Guidance

Structured Analysis Framework

Step 1: Restate the Problem

Step 2: Generate Ranked Hypotheses

Step 3: Systematic Verification

Reasoning Principles

Decision Framework

Effort Estimation

Common Failure Patterns

Traps to Avoid

Output Template

Files

Compare with similar skills

Similar skills

More from TechDufus/oh-my-claude

Related

Questions about Debugger