Debug
Skill Verified ActiveDiagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
To help developers quickly diagnose and understand issues occurring within their OMC development environment or repository by systematically analyzing available evidence.
Features
- Diagnose OMC session/repo state
- Analyze logs, traces, and state
- Focused reproduction of issues
- Identify failure signals and root causes
- Recommend corrective steps
Use Cases
- Use when encountering confusing runtime behavior in OMC.
- Use when workflow breaks or tests fail unexpectedly.
- Use to understand the root cause of orchestration or agent flow issues.
Non-Goals
- Prescribing broad rewrites before isolating failures.
- Providing general debugging advice outside of the current session/repo context.
- Acting as a code linter or static analysis tool.
Practical Utility
- info:Usage examplesWhile the SKILL.md outlines a workflow, concrete end-to-end examples showing input, invocation, and output are missing.
- info:Edge casesThe skill mentions distinguishing symptoms from root causes and recommending fixes, but specific failure modes and recovery steps are not detailed.
Installation
First, add the marketplace
/plugin marketplace add Yeachan-Heo/oh-my-claudecode/plugin install oh-my-claudecode@omcQuality Score
VerifiedTrust Signals
Similar Extensions
Query Agent Events
99Bug-investigation tool for the Netdata agent-events ingestion namespace -- triage crashes, panics, fatals across the fleet by downloading events of interest and clustering locally. Covers the three transports (Cloud API and direct agent API are primary; ssh is operator-only), the verified AE_* field map and enum meanings, the dedup model (23h client-side per agent and event signature), the after-the-fact event timing (POST only on agent restart), and the Netdata systemd-journal plugin multi-value filter syntax (FIELD in A, B, C) AND ... Use when investigating crashes / panics / fatals; when grepping for events touching a specific function or file or version; when looking for regressions across versions; when an agent is reported crashing in a way you want to triage. Ships scripts get-events.sh and analyze-events.sh that fetch events with index-friendly filters and compute group-by stats. Defaults to last 24 hours and to the latest stable plus latest 2-3 nightlies.
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Ctx Doctor
100Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes