debug

Diagnose OMC/Claude-Code session issues by analyzing logs, traces, and state.

6|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ImL1s/flutter-claude-skills --skill debug-iml1s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/ImL1s/flutter-claude-skills/tree/main/skills/debug
Command: npx skills add https://github.com/ImL1s/flutter-claude-skills --skill debug-iml1s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and triage OMC/Claude-Code session issues using logs, traces, and state to surface the real failure signal quickly and clearly.

Core Features & Use Cases

  • Structured issue analysis across traces, state dumps, and session context
  • Reproduce and validate root-cause hypotheses with minimal steps
  • Clear, actionable next steps for debugging and remediation in complex workflows

Quick Start

Describe the issue you are facing and provide any relevant logs to begin diagnosis.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I diagnose Claude-Code session instability using logs and traces?

Diagnose Claude-Code session instability by analyzing logs, traces, and state dumps to surface failure signals. The Skill structures issue analysis across session context to validate root-cause hypotheses with minimal steps.

What is the best way to find the root cause of OMC workflow breakages?

Finding the root cause of OMC workflow breakages requires coordinating evidence from traces and state dumps. This approach reproduces and validates root-cause hypotheses, providing clear next actions for debugging complex runtime behavior.

Do I need reproducible steps to triage confusing Claude-Code runtime behavior?

Reproducible steps are required to triage confusing Claude-Code runtime behavior. The diagnosis process requires access to trace tools, state dumps, and reproducible steps to coordinate evidence and validate root-cause hypotheses effectively.

How does structured trace analysis work for local repo debugging?

Structured trace analysis for local repo debugging works by examining logs, traces, and session state to surface real failure signals quickly. It coordinates evidence to formulate and validate root-cause hypotheses for actionable remediation.

Why does my Claude-Code session show confusing runtime behavior?

Confusing runtime behavior in Claude-Code sessions can stem from complex workflow breakages or state instability. Analyzing traces and state dumps surfaces the real failure signal, allowing you to reproduce and validate the root cause.