debug is agent-read markdown (skill) from chan4lk/specclaw: Use when a bug, test failure, build failure, or unexpected behaviour is reported or observed, before proposing any fix..
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
# specclaw debug
**First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
## The Iron Law
**No fix without a stated root cause.**
One hypothesis at a time. The smallest change that tests *that* hypothesis. A wrong hypothesis is
withdrawn and replaced — never fixed on top of.
The cost of breaking this law is not a wasted turn. It is a codebase carrying three speculative
changes, none of which addressed the problem, and no record of what was ruled out — so the next
person starts from zero.
## Phase 1 — Evidence
Before forming any theory:
1. **Read the whole error.** Not the first line. Stack traces name the boundary that failed; the
first line names the boundary that noticed.
2. **Reproduce it with one command.** Write that command down — it is the record's `reproduce` field
and the thing the fix must be proved against. If it cannot be reproduced on demand, say so
explicitly; an unreproducible bug is a different investigation.
…
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.
B 16 of 17 checks passed. Deterministic, no model, same answer every run.
fail: Frontmatter declares a name
pass: Frontmatter block present
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (7740 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
chan4lk/specclaw · 12 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iec432u3v4zrzcx5
GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/debug
GET https://markdownregistry.com/api/v1/blob/6b155f270f4d0f476d04b6ca6c13f62872d111fcb18d18048592d8813c11594f
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.
chan4lk/specclaw · .agents/skills/specclaw/SKILL.md · Run the SpecClaw spec-driven lifecycle in this repository when a request needs proposal, planning, build, verification…
chan4lk/specclaw · plugins/specclaw/skills/archive/SKILL.md · Move a completed change to .specclaw/changes/archive/ under its existing name. Closes the GitHub Issue (if sync is…
chan4lk/specclaw · plugins/specclaw/skills/auth-azdo/SKILL.md · Interactive setup for Azure DevOps authentication. Prompts for organization, project, and repo, validates a Personal…
chan4lk/specclaw · plugins/specclaw/skills/author-spec/SKILL.md · Interactively co-author spec.md for an approved proposal via the spec-author subagent. The agent walks the user through…
chan4lk/specclaw · plugins/specclaw/skills/auto/SKILL.md · Run the propose → plan → build → verify lifecycle autonomously across the queue of active changes. Advanced — requires…
chan4lk/specclaw · plugins/specclaw/skills/azdo-issue/SKILL.md · Create or update an Azure Boards Work Item that mirrors this proposal. Targets Azure DevOps Boards (Features / User…
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…
