receiving-code-review
OBobra/superpowers298k2,631 new stars in the last 7 days
debug
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
- Star
- 39,841
- Category
- Coding & debugging
- License
- MIT
- Last commit
- Oct 13, 2026
skills/debug/SKILL.md
View on GitHubDebug
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
Similar Skills
requesting-code-review
OBobra/superpowers298k2,631 new stars in the last 7 days
systematic-debugging
OBobra/superpowers298k2,631 new stars in the last 7 days
code-review
MAmattpocock/skills288k10,178 new stars in the last 7 days
codebase-design
MAmattpocock/skills288k10,178 new stars in the last 7 days
scaffold-exercises
MAmattpocock/skills288k10,178 new stars in the last 7 days