debugging

Diagnose runtime failures through hypothesis ranking, instrumentation, and verified fixes.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/UtsavBalar1231/oh-my-claudeagent --skill debugging-utsavbalar1231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/UtsavBalar1231/oh-my-claudeagent/tree/main/skills/debugging
Command: npx skills add https://github.com/UtsavBalar1231/oh-my-claudeagent --skill debugging-utsavbalar1231

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Runtime bugs like crashes, wrong output, race conditions, and intermittent failures are hard to fix because developers often patch symptoms without understanding the root cause. This Skill enforces a disciplined debugging loop so every fix is backed by observed evidence, not guesswork. ## Core Features & Use Cases - Structured Debugging Loop: Reproduce the failure, form at least three ranked falsifiable hypotheses, instrument before modifying, test each hypothesis, fix only after confirmation, and verify adjacent behavior is unchanged. - Concurrency and Environment Diagnostics: Reference guides cover timing-dependent failures, use-after-release patterns, and works-locally-but-not-in-prod environment diffs. - Escalation and Hygiene Rules: After two failed fix attempts, escalate with a full attempt timeline; all temporary instrumentation is tracked and removed before the task is done. - Use Case: A flaky test fails only under load in CI. Use this Skill to form ranked hypotheses about shared-state ordering, force the suspected interleaving with a controlled delay, confirm the cause, and ship a verified fix. ## Quick Start Ask the agent to debug why your application crashes intermittently in production but works locally, and have it follow the reproduce-hypothesize-instrument-fix-verify loop.

Frequently Asked Questions about debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug an intermittent failure that only happens in production?

Start by building a repro that fails on demand, then form at least three ranked hypotheses each with a discriminating test. For environment differences, diff dependency versions, configuration, data shape, and resource limits between environments, then toggle one variable to confirm the cause.

How to find the root cause of a race condition?

Race conditions are timing-dependent, so force the suspected interleaving with a lock, delay, or reduced worker count. If the bug becomes reliable when you control the ordering, the hypothesis is confirmed; if it stays equally rare, move to the next hypothesis.

What is the difference between fixing a symptom and fixing a bug?

A symptom fix makes the visible failure stop; a real fix lets you state the causal chain and prove it with a toggle: apply the fix and the failure goes away, revert it and the failure returns. Without that toggle you have a correlation, not a root cause.

When should I escalate a debugging session instead of retrying?

After two failed fix attempts on the same bug, stop iterating alone. Two failed rounds signal your mental model of the system is wrong, so hand over the attempt timeline: each hypothesis, what its discriminating test showed, and why it was ruled out.

Does this debugging approach cover build failures and type errors?

No. Build failures, compile and type errors, and toolchain or dependency breakage belong to the hephaestus flow. This Skill owns only misbehavior that appears once code is running: crashes, hangs, wrong output, races, and silent failures.