debug
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
Works with
--- name: debug description: Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction license: MIT --- # 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
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
