debug is agent-read markdown (skill) from lstr-1/skills: Use when encountering any bug, test failure, build break, or unexpected behavior — runs a 4-phase systematic debugging process before proposing any fix. Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Produces a `.orchestrator/debug/` artifact the fixer agent must reference..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Debug Skill
> 4-phase root-cause investigation. Iron Law: no fix without root cause.
## When to use
- Any test failure (unit, integration, E2E)
- Build break or compile error
- Runtime exception in production code
- Performance regression
- Integration issue between modules
- "It worked yesterday" bugs
## When NOT to use
- Feature implementation (use `/plan` or wave-executor)
- Pure refactoring with no broken behavior
- Style/lint fixes with no behavioral impact
## Phase 0: Bootstrap Gate
Read `skills/_shared/bootstrap-gate.md` and execute the gate check. If the gate is CLOSED, invoke `skills/bootstrap/SKILL.md` and wait for completion before proceeding. If the gate is OPEN, continue to Phase 1.
<HARD-GATE>
Do NOT proceed past Phase 0 if GATE_CLOSED. There is no bypass. Refer to `skills/_shared/bootstrap-gate.md` for the full HARD-GATE constraints.
</HARD-GATE>
## The Iron Law
> **NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.**
No matter how obvious the fix looks, complete Phase 1 (Root Cause Investigation) and produce the artifact BEFORE writing any fix code. This is non-negotiable.
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_vbmhdslwcabkcsls
GET https://markdownregistry.com/api/v1/resolve?ref=lstr-1/skills/debug
GET https://markdownregistry.com/api/v1/blob/6f2b5fc01ad9fc797fca01d4766994740e4c7077fc264434f19772e939e45a1c
Your agent 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.
lstr-1/skills · create-skill/SKILL.md · Use when the user wants to create, design, or generate a new AI agent skill (SKILL.md) from a problem description. This…
lstr-1/skills · monitor-startup-dach/SKILL.md · Fetch the top-25 posts from r/StartupDACH/hot.json, classify each into six deterministic German intent clusters…
lstr-1/skills · nlm-meta-study/SKILL.md · Create scientific meta-studies on any topic using Gemini Notebook (NotebookLM). Invoke for systematic reviews…
lstr-1/skills · orchestrator/skills/architecture/SKILL.md · Use when the user asks to improve architecture, find refactoring opportunities, surface deepening opportunities…
lstr-1/skills · orchestrator/skills/autopilot/SKILL.md · Use this skill when running an autonomous session-orchestration loop. Chains session-start → session-plan →…
lstr-1/skills · orchestrator/skills/bootstrap/SKILL.md · Use this skill when scaffolding the minimum repository structure required by orchestrator. Invoked automatically by the…
lstr-1/skills · orchestrator/skills/brainstorm/SKILL.md · Use when you have a feature idea but the scope or UX is still ambiguous — runs a lightweight Socratic design dialogue…
lstr-1/skills · orchestrator/skills/claude-md-drift-check/SKILL.md · Use when detecting drift between CLAUDE.md (or AGENTS.md, the Codex CLI alias) / _meta narrative and live repository…
lstr-1/skills · orchestrator/skills/daily/SKILL.md · Use this skill when creating today's daily note in the Meta-Vault (03-daily/YYYY-MM-DD.md) with valid…
lstr-1/skills · orchestrator/skills/debug/SKILL.md · Use when encountering any bug, test failure, build break, or unexpected behavior — runs a 4-phase systematic debugging…
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…
arbiterforge/codearbiter · plugins/ca-codex/routines/debug/SKILL.md · Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a…
arbiterforge/codearbiter · plugins/ca/skills/debug/SKILL.md · Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a…
arbiterforge/codearbiter · plugins/ca-pi/routines/debug/SKILL.md · Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a…
