- name
SKILL.md
Tệp skill vẫn nằm trong kho mã của nhà phát hành.
Dán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add code-yeongyu/oh-my-openagent --skill debugging -a cursor -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add code-yeongyu/oh-my-openagent --skill debugging -a claude-code -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add code-yeongyu/oh-my-openagent --skill debugging -a codex -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add code-yeongyu/oh-my-openagent --skill debugging -a grok -yGửi tin nhắn đã sao chép trong cuộc trò chuyện Grok Bot. Bot sẽ lấy tệp SKILL.md này từ GitHub và thêm vào bộ skill mà mọi Bot của bạn dùng chung.
Install this skill: https://github.com/code-yeongyu/oh-my-openagent/tree/HEAD/packages/shared-skills/skills/debuggingTừ nhà phát hành
You are a hypothesis-driven debugger. Two disciplines apply regardless of language, runtime, or whether you have source:
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.
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.
The methodology is language-agnostic. The commands to launch, attach, breakpoint, and inspect are not. Open the matching reference before Phase 0. Not during. Not after.
If you cannot honestly say you just opened the reference for your runtime, open it now.
🚨 Native binary vs bundled binary — check before committing:
file ./targetcalls them both Mach-O / ELF. The 30-second discriminator isdu -h ./target(50 MB+ suspect bundled) plusstrings -n 12 ./target | rg -iE 'bun|node_modules|webpack|esbuild|deno|pkg/lib|electron|pyinstaller|nexe|NODE_SEA_FUSE|tauri'. If hits → bundled-js-binary.md. If clean → native-binary.md.
These are not "optional extras". They are the correct tool in their domain, and anything else is slower and less reliable. If the bug fits the domain, you MUST use the tool. Read the reference first to know how.
Failing to use these tools in their domain is a process failure, not a stylistic choice. If the bug is in a browser and you did Phase 8 without Playwright, you are doing it wrong. If the bug is in a stripped binary and you read hex with xxd, you are doing it wrong. The references tell you how. Read them.
Each phase has exactly one reference. Read it as you enter the phase — not in advance, not from memory. The references are self-contained and short.
Phase references are short by design. Reading one takes a minute. Skipping one costs an hour.
These are not phases — read them when the situation calls for them:
references/runtimes/<runtime>.md. Read it.references/tools/*.md. Read them.references/methodology/00-setup.md and start Phase 0.The references are the skill. This file is an index.
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 re
---name: debuggingdescription: Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles…---# packages/shared-skills/skills/debugging/SKILL.mdTổng quan
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.
Câu hỏi thường gặp
Tải packages/shared-skills/skills/debugging/SKILL.md từ nhà phát hành, hoặc sao chép đường dẫn và mở kho mã. PlugMCP chỉ liệt kê skill và không lưu trữ tệp này.
Nhà phát hành duy trì nó tại https://github.com/code-yeongyu/oh-my-openagent.
Claude, Cursor, Codex và Grok Build có thể đọc tệp SKILL.md mà bạn thêm từ kho mã của nhà phát hành. Grok Bot cài đặt skill khi bạn gửi liên kết thư mục GitHub của skill trong cuộc trò chuyện.
dap.mjsAny time you would drive a debugger through a PTY and screen-scrape its text. Debuggers already speak the machine-readable Debug Adapter Protocol (debugpy, dlv dap, lldb-dap, js-debug); this bundled script drives it with bounded, monitorable output. Prefer it over scraping gdb/pdb whenever the debugger speaks DAP. Design modeled on oh-my-pi's debug tool (github.com/can1357/oh-my-pi). |
| 📖 references/tools/dap.md |
| references/methodology/06-fix.md |
| 8 | Manual QA — actually use the system (tmux for CLI, Playwright for browser, real curl for API, real repro for binary) | references/methodology/08-qa.md |
| 9 | Cleanup — walk the journal, revert every artifact, verify git diff shows only fix + test | references/methodology/09-cleanup.md |
| 10 | Final verification — four evidence gates before declaring done | references/methodology/09-cleanup.md |