Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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
The line at the top of this page pins the label git:20260503.16cdfd3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_tw7mjcqery76d6sp
GET https://markdownregistry.com/api/v1/resolve?ref=naimkatiman/continuous-improvement/debug
GET https://markdownregistry.com/api/v1/blob/b54c1263f4a9d0e40fbb5025cf25468737c3e92fcad31f97f67d6c368a52fdc2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
naimkatiman/continuous-improvement · plugins/continuous-improvement/skills/audit/SKILL.md · Enforces Law 4 (Verify Before Reporting) of the 7 Laws of AI Agent Discipline. Audits a window of recent commits for…
naimkatiman/continuous-improvement · plugins/continuous-improvement/skills/deploy-receipt/SKILL.md · Enforces Law 4 (Verify Before Reporting) of the 7 Laws of AI Agent Discipline at the deploy seam. A merge into a branch…
naimkatiman/continuous-improvement · plugins/continuous-improvement/skills/gateguard/SKILL.md · Enforces Law 1 (Research Before Executing) of the 7 Laws of AI Agent Discipline. Fact-forcing gate that blocks…
naimkatiman/continuous-improvement · plugins/continuous-improvement/skills/goal-monitor/SKILL.md · Enforces Law 2 (Plan Is Sacred) of the 7 Laws of AI Agent Discipline. Detects when a session has drifted away from its…
naimkatiman/continuous-improvement · plugins/continuous-improvement/skills/grill-me/SKILL.md · Enforces Law 1 (Research Before Executing) of the 7 Laws of AI Agent Discipline. Interview the user relentlessly about…
naimkatiman/continuous-improvement · plugins/continuous-improvement/skills/grill-with-docs/SKILL.md · Enforces Law 1 (Research Before Executing) and Law 7 (Learn From Every Session) of the 7 Laws of AI Agent Discipline…
naimkatiman/continuous-improvement · plugins/continuous-improvement/skills/handoff/SKILL.md · Enforces Law 5 (Reflect After Every Session) of the 7 Laws of AI Agent Discipline. Compact the current conversation…
yeachan-heo/oh-my-claudecode · skills/debug/SKILL.md · Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
nanocoai/nanoclaw · .claude/skills/debug/SKILL.md · Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to…
agentic-community/mcp-gateway-registry · .claude/skills/debug/SKILL.md · Debug issues in the MCP Gateway Registry using first-principles thinking. Invoke when something is broken, timing out…
suboss87/fdeops · skills/debug/SKILL.md · Investigate a failure, regression or incorrect result in an integration or application, even before it can be…
rsmdt/the-startup · plugins/start/skills/debug/SKILL.md · Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
ericrisco/rsc-harness · skills/debug/SKILL.md · Use when something is broken — a failing or flaky test, crash, wrong result or regression — and the root cause must be…
fcakyon/labrat · plugin/skills/debug/SKILL.md · Evidence-before-action diagnosis of failing ML experiments. Probes the system before guessing causes, process list…
