# Debug

> Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

- Skill: `iml1s/debug` (Agent Skill)
- Install (CLI): `npx skillmds@latest add iml1s/debug`
- Raw SKILL.md: https://api.skillmd.com/api/skills/iml1s/debug/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ImL1s (https://skillmd.com/u/iml1s)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/iml1s/debug

---


# 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
1. Read the user’s issue description carefully.
2. Inspect the most relevant local evidence first:
   - trace tools
   - state tools
   - notepad / project memory when relevant
   - failing tests or commands
3. Reproduce the issue narrowly if possible.
4. Distinguish symptoms from root cause.
5. 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.

## Output
- Observed failure
- Root-cause hypothesis
- Evidence for that hypothesis
- Smallest next action

## Related skills

- **`systematic-debugging`** — **DISAMBIGUATION**: systematic-debugging is for debugging app code and production issues. debug is for diagnosing OMC/Claude-Code session and workflow issues. Use systematic-debugging for app crashes/bugs; use debug for harness/session problems.