debug

Name: debug
Availability: InStock
Author: xdkp

Diagnose broken OMC or Claude Code workflows using trace and state evidence.

Updated May 20, 2026

Search Tags:#debugging #logs #orchestration #trace #state #workflow diagnosis

Ready to run

npx skills add https://github.com/xdkp/oh-my-claudecode --skill debug-xdkp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/xdkp/oh-my-claudecode/tree/main/skills/debug
Command: npx skills add https://github.com/xdkp/oh-my-claudecode --skill debug-xdkp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an OMC/Claude-Code workflow breaks or behaves unexpectedly, this Skill helps you diagnose the underlying cause using real session evidence instead of guesses.

Core Features & Use Cases

Evidence-first diagnosis: Collects and interprets trace/state artifacts and relevant session memory to identify the actual failure signal.
Focused reproduction: Narrows the problem by reproducing it in the smallest possible scope to confirm cause versus symptoms.
Actionable recovery guidance: Produces clear outputs (observed failure, hypothesis, evidence, and smallest next action) to move you forward immediately.

Quick Start

Ask an AI to use the debug skill to diagnose your current OMC session by examining your trace and state logs and then recommending the smallest next verification step.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug a broken OMC or Claude Code workflow using trace logs?▼

You diagnose workflow issues by collecting and interpreting trace and state artifacts alongside relevant session memory to identify the real failure signal. This evidence-first approach separates symptoms from root causes.

What is the best way to diagnose confusing runtime behavior during an active Claude Code session?▼

The best way to diagnose confusing runtime behavior is to examine trace and state logs to separate symptoms from the root cause. This yields an observed failure, a root-cause hypothesis, supporting evidence, and the smallest next corrective action.

How do I reproduce an orchestration issue in the smallest possible scope?▼

You reproduce an orchestration issue by narrowing the problem to the smallest possible scope to confirm cause versus symptoms. This focused reproduction uses trace and state evidence to validate the root-cause hypothesis.

Can I use state and trace artifacts to fix hook or agent-flow problems?▼

Yes, you can diagnose hook or agent-flow problems by interpreting state and trace artifacts from your active session. This evidence identifies the failure signal and outputs the smallest next verification step for immediate recovery.

Why does my OMC workflow keep failing and how do I find the root cause?▼

Your OMC workflow fails due to an underlying cause that requires evidence-first diagnosis. By examining trace and state logs, you can separate confusing symptoms from the actual root cause and determine the smallest next corrective action.