Catalog
yeachan-heo/debug

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

v1.0LATEST
NewUpdated Sep 9, 2026

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
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

76/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

88

Quality

72

Clarity

78

Completeness

68

Summary

This skill guides an agent to diagnose OMC (Claude-Code) session or repository problems by inspecting logs, traces, and state. It provides a systematic workflow for identifying root causes and recommending minimal corrective actions without broad rewrites.

Detected Capabilities

log inspectiontrace analysisstate inspectiontest/command executionissue reproductionsession diagnostics

Trigger Keywords

Phrases that agents use to match this skill to user intent.

debug session failurediagnose workflow issueisolate runtime errorreproduce test failuretrace log analysisOMC session diagnostics

Use Cases

  • Diagnosing orchestration or hook-level failures in Claude-Code sessions
  • Isolating runtime errors in agent workflows
  • Reproducing and narrowing down failing tests or commands
  • Distinguishing symptoms from root causes in project breakage
  • Identifying product/runtime bugs versus application code issues

Quality Notes

  • Skill is tightly scoped to diagnostic workflows—no destructive operations or external access
  • Clear problem-solving methodology with explicit rules (prefer evidence, isolate before rewriting)
  • References specific diagnostic surfaces (trace tools, state tools, notepad) suggesting integration with OMC runtime
  • Output format is well-defined: observed failure, hypothesis, evidence, next action
  • Limitations could be more explicit (e.g., does not prescribe code fixes, only diagnostics)
  • No supporting documentation or examples of how to interpret traces/state output
Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use yeachan-heo/debug in your dev environment

Command Palette

Search for a command to run...