Agent skill

Hypothesis-Driven Debugging

by code-yeongyu in code-yeongyu/oh-my-openagent

Runs a hypothesis-driven debugging loop for crashes, hangs and silent failures in any language, grounding every claim in runtime evidence and locking the fix with a test.

Custom licenceAuto-check passedDevelopment

Install Hypothesis-Driven Debugging

skills CLI
$ npx skills add code-yeongyu/oh-my-openagent --skill debugging -a claude-code

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

GitHub CLI
$ gh skill install code-yeongyu/oh-my-openagent debugging --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/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/shared-skills/skills/debugging .claude/skills/debugging && 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
debugging
GitHub stars
70k
Token cost
~3.2k tokens
SKILL.md length
1,506 words
Files
26 (incl. references)
Skills in repo
44
Repo updated
First seen
Licence
Custom licence

At a glance

Runs a hypothesis-driven debugging loop for crashes, hangs and silent failures in any language, grounding every claim in runtime evidence and locking the fix with a test.

  • Works in 2 steps: Runtime truth beats code reading. Every… → Leave no trace. Debugging creates…
  • Chasing a crash, hang or silent failure without an obvious cause
  • SKILL.md covers Runtime Setup — MANDATORY…, Specialist Tools — ACTIVELY…, The Phase Loop — READ THE… and Non-Negotiable Safety Invariants, plus 1 more section
  • Runs JavaScript scripts from its folder; calls git, poetry and node

What it does

The skill rests on two rules. Runtime truth beats code reading, so every claim about why a bug happens must come from observed state. And leave no trace, so every artifact created while debugging is journaled and removed before the task is done. The SKILL.md is deliberately small and works as a map; the knowledge sits in the references, which must be read before attaching a debugger or running commands from their domain.

The references include runtime guides for Python, Node, Go, Rust, native binaries and bundled JavaScript binaries, methodology files for setup, investigation, flaky triage, an oracle triple, escalation, fixing, QA and cleanup, and a dap.mjs script. The method escalates to orthogonal oracle angles and finishes by locking the fix with a failing test. It targets crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior and reverse engineering.

When your agent uses it

  • Chasing a crash, hang or silent failure without an obvious cause
  • Investigating a memory leak or async misbehavior
  • Triaging a flaky test
  • Needing the fix locked in with a failing test

Example prompts

  • “The worker hangs after the third job and logs nothing. Debug it from runtime evidence.”
  • “Find why this Node script returns the wrong response and lock the fix with a failing test first.”
  • “Triage this flaky test and tell me what the evidence says.”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Runtime truth beats code reading. Every claim about why the bug happens must come from observed state — never from a plausible story spun…
  2. Leave no trace. Debugging creates artifacts. Every artifact is journaled and removed before you call the task done.

What it can do on your machine

Read from SKILL.md and the folder at commit cbd7dd2. 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

    Ships script files (JavaScript, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • poetry
    • node
    • go
    • rg
    • deno

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Hypothesis-Driven Debugging loads about 3.2k tokens when it runs, and up to ~53k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 1,506 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~53k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,506 words (~3,168 tokens).

“You are a hypothesis-driven debugger. Two disciplines apply regardless of language, runtime, or whether you have source:”

— opening of SKILL.md by code-yeongyu, Custom licence
name
debugging

Read the full SKILL.md on GitHub

Files

SKILL.md and 25 other files (references) in packages/shared-skills/skills/debugging of code-yeongyu/oh-my-openagent.

  • SKILL.md
  • references/methodology/00-setup.md
  • references/methodology/02-investigate.md
  • references/methodology/03-flaky-triage.md
  • references/methodology/04-oracle-triple.md
  • references/methodology/05-escalate.md
  • references/methodology/06-fix.md
  • references/methodology/08-qa.md
  • references/methodology/09-cleanup.md
  • references/methodology/partial-runtime-evidence.md
  • references/runtimes/bundled-js-binary.md
  • references/runtimes/go.md
  • references/runtimes/native-binary.md
  • references/runtimes/node.md
  • references/runtimes/python.md
  • references/runtimes/rust.md
  • references/scripts/dap.mjs
  • … and 9 more

Open the folder on GitHubat commit cbd7dd2

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in code-yeongyu/oh-my-openagent, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Hypothesis-Driven Debugging 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.

Hypothesis-Driven Debugging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hypothesis-Driven Debugging this skillcode-yeongyu/oh-my-openagent70k—~3.2kAutomated safety check: PassCustom licence
Systematic DebuggingChrisWiles/claude-code-showcase6.1k3 repos~1.2kAutomated safety check: PassNone
Debugging and Error Recoveryaddyosmani/agent-skills102k1 repos~2.6kAutomated safety check: PassMIT
Systematic Debugginged3dai/ed3d-plugins2503 repos~2.4kAutomated safety check: PassNone
Debugging And Error Recoveryabashev/vfs-s31066 repos~2.6kAutomated safety check: PassApache-2.0
Veomni DebugByteDance-Seed/VeOmni2.2k—~2.8kAutomated safety check: PassApache-2.0

Similar skills

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

    102k GitHub starsUsed in 1 repo~2.6k tokens
    DevelopmentAuto-check passed
  • Systematic Debugging

    ed3dai/ed3d-plugins

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis…

    250 GitHub starsUsed in 3 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Guides systematic root-cause debugging. An agent skill from abashev/vfs-s3.

    106 GitHub starsUsed in 6 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Veomni Debug

    ByteDance-Seed/VeOmni

    A skill your agent uses for ANY bug, error, crash, wrong output, loss divergence, gradient explosion, test failure, CUDA error, distributed training hang, checkpoint load failure, or unexpected…

    2.2k GitHub stars~2.8k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Root Cause Debugging

    jsmastery-pro/skills

    Runs a reproduce, localize, hypothesize, test, fix and verify loop to find a bug's root cause, applies the minimal fix and hands off a regression test.

    1.4k GitHub stars~1.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

More from code-yeongyu/oh-my-openagent

All 44 skills in this repo
  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Browser Control with Omowright

    code-yeongyu/oh-my-openagent

    Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.

    70k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Codex Plugin QA

    code-yeongyu/oh-my-openagent

    Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.

    70k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Coding Agent Session Finder

    code-yeongyu/oh-my-openagent

    Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.

    70k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • LSP Setup

    code-yeongyu/oh-my-openagent

    Detects which languages a project uses, installs the matching language server, writes its config and checks it with a real call so diagnostics and go-to-definition work.

    70k GitHub stars~1.4k tokensUpdated today
    Auto-check: notes
  • OpenCode QA Toolkit

    code-yeongyu/oh-my-openagent

    Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.

    70k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Categories

Questions about Hypothesis-Driven Debugging

What does Hypothesis-Driven Debugging do?

Runs a hypothesis-driven debugging loop for crashes, hangs and silent failures in any language, grounding every claim in runtime evidence and locking the fix with a test. The skill rests on two rules. Runtime truth beats code reading, so every claim about why a bug happens must come from observed state.

When should I use Hypothesis-Driven Debugging?

Hypothesis-Driven Debugging fits situations like: chasing a crash, hang or silent failure without an obvious cause; investigating a memory leak or async misbehavior; triaging a flaky test; needing the fix locked in with a failing test.

How do I install Hypothesis-Driven Debugging in Claude Code?

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

How do I install Hypothesis-Driven Debugging in Codex?

Run `npx skills add code-yeongyu/oh-my-openagent --skill debugging -a codex`. Or copy the skill folder (packages/shared-skills/skills/debugging in code-yeongyu/oh-my-openagent) into .agents/skills/debugging in your project. Codex loads it when a task matches its description.

Can I use Hypothesis-Driven Debugging 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 code-yeongyu/oh-my-openagent --skill debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging, .gemini/skills/debugging, .github/skills/debugging and .opencode/skills/debugging in your project.

What does Hypothesis-Driven Debugging need to run?

Going by SKILL.md and its folder, Hypothesis-Driven Debugging needs JavaScript for the scripts in its folder and the command-line tools its instructions call (git, poetry, node, go, rg and deno).

Does Hypothesis-Driven Debugging access the network?

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

Is Hypothesis-Driven Debugging 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 Hypothesis-Driven Debugging use?

Hypothesis-Driven Debugging has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Hypothesis-Driven Debugging use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 50k tokens, read only when the agent opens those files.

What are the alternatives to Hypothesis-Driven Debugging?

Skills that share tags, products or a category with Hypothesis-Driven Debugging: Systematic Debugging (ChrisWiles/claude-code-showcase, 6.1k stars), Debugging and Error Recovery (addyosmani/agent-skills, 102k stars), Systematic Debugging (ed3dai/ed3d-plugins, 250 stars) and Debugging And Error Recovery (abashev/vfs-s3, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hypothesis-Driven Debugging?

code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,850 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 7, 2026.

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