debug
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
- Installs
- 640
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill debug- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads debug automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Debug
Use this skill when the user wants help diagnosing a current OMC/Claude-Code session problem, workflow breakage, or confusing runtime behavior.
Goal
Find the real failure signal quickly and explain the next corrective step.
Workflow
- Read the user’s issue description carefully.
- Inspect the most relevant local evidence first:
- trace tools
- state tools
- notepad / project memory when relevant
- failing tests or commands
- Reproduce the issue narrowly if possible.
- Distinguish symptoms from root cause.
- Recommend the smallest next fix or verification step.
Rules
- Prefer real evidence over guesses.
- Use the trace/state surfaces when the issue involves orchestration, hooks, or agent flow.
- If the issue is actually a product/runtime bug rather than app code, say so plainly.
- Do not prescribe broad rewrites before isolating the failure.
- Tag temporary debug output
[DEBUG-<4hex>]; cleanup is then a single grep. - Redact secrets from logs and traces before they leave the session.
- If the failure traces to a missing or wrong seam, say so as the finding and point at
refitorarchitecture-survey— the environment lesson outlives the fix.
Output
- Observed failure
- Root-cause hypothesis
- Evidence for that hypothesis
- Smallest next action
FAQ
What does the debug skill do?
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
How do I install debug?
Run npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill debug in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/debug/ (personal) or .claude/skills/debug/ (project).
Which AI agents can use debug?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is debug safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains debug?
It is published by yeachan-heo in yeachan-heo/oh-my-claudecode. It has 640 recorded installs.
More from yeachan-heo/oh-my-claudecode
ai-slop-cleaner
yeachan-heo/oh-my-claudecode
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
ralplan
yeachan-heo/oh-my-claudecode
Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution
hud
yeachan-heo/oh-my-claudecode
Configure HUD display options (layout, presets, display elements)
deepinit
yeachan-heo/oh-my-claudecode
Deep codebase initialization with hierarchical AGENTS.md documentation
deep-interview
yeachan-heo/oh-my-claudecode
Socratic deep interview with mathematical ambiguity gating before explicit execution approval
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.