debug

Diagnose OMC/Claude-Code session failures by aggregating logs, traces, and state.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill debug-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/debug
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill debug-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initial diagnosis of OMC/Claude-Code session problems by correlating logs, traces, and current state to surface the true failure signal.

Core Features & Use Cases

  • Integrated log/trace/state analysis to identify root causes
  • Narrow reproduction steps to verify hypotheses and expedite fixes
  • Incident-focused guidance that translates findings into actionable next steps

Quick Start

Describe your issue succinctly and trigger a diagnostic session to begin analysis.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I diagnose issues in an OMC or Claude-Code session using logs and traces?

Diagnose OMC or Claude-Code session issues by aggregating logs, execution traces, and current runtime state to surface the real failure signal. This structured diagnostic workflow frames the issue, gathers evidence, forms a root-cause hypothesis, and validates it to isolate the problem.

What is the best way to reproduce a runtime code execution error for debugging?

The best way to reproduce a code execution error is to use a diagnostic workflow that narrows reproduction steps based on correlated logs and traces. This quickly verifies your root-cause hypotheses against the current state and expedites the final fix.

Can I use this diagnostic workflow for deployment incidents and runtime sessions?

Yes, you can use this diagnostic workflow for runtime sessions, code execution issues, and deployment workflows. It is specifically applicable to environments where quick replication and isolation of the failure signal are possible.

How does correlating logs and current state help find a root cause?

Correlating logs and current state helps find a root cause by integrating multiple evidence sources to filter out noise and surface the true failure signal. This integrated analysis directly translates diagnostic findings into actionable, smallest-next-action recommendations.

What should I do when my Claude-Code session fails and I cannot isolate the failure signal?

When your Claude-Code session fails, trigger a diagnostic session and describe the issue succinctly. The diagnostic process aggregates logs, execution traces, and state to frame the incident, gather evidence, test hypotheses, and recommend a smallest-next-action.