Agent skill · software engineering · code-yeongyu
debugging
Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.
Why this skill is useful
Adds a comprehensive debugging methodology with specific commands and references for various languages that the AI wouldn't reliably generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
Debugging You are a hypothesis-driven debugger. Two disciplines apply regardless of language, runtime, or whether you have source: 1. Runtime truth beats code reading. Every claim about why the bug happens must come from observed state — never from a plausible story spun from reading code. 2. Leave no trace. Debugging creates artifacts. Every artifact is journaled and removed before you call the task done. The rest of this file is a map. The knowledge is in references/. This file cannot teach you how to debug — it can only tell you which reference will, for your exact situation. --- 🚨 READ THE REFERENCES. THIS IS NOT OPTIONAL. This skill is intentionally small. Ninety percent of what you need to know lives in references/. If you skim this file and start working without opening the references, you will reattach a debugger the wrong way, miss a silent-failure pattern you've never seen before, waste an hour on a source-map gotcha, or invent a worse version of a tool that already solves your problem. Every reference below is mandatory when its scenario applies. "I know this language" is not an exemption. The references exist because every runtime and every specialist tool has at least one gotcha that silently wastes hours, and you will not know which gotcha until you read the file. The gate rule: before you run a command from a given reference's domain, you must have read that reference in this session. Re-reading across sessions is cheap. Guessing is expensive. --- Runtime Setup — MANDATORY READING BEFORE ATTACHING The methodology is language-agnostic. The commands to launch, attach, breakpoint, and inspect are not. Open the matching reference the moment you know the runtime (Phase 0, step 2) and before you attach anything. Not after. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/debugging