debug SKILL.md skillB

debug from chan4lk/specclaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add chan4lk/specclaw/debug@git:20261011.0845a18

Pins git:20261011.0845a18 in mdr.lock. Pin the fingerprint instead.

Audit grade: B, 16 of 17 checks passed
Kind: SKILL.md skill
Repository: chan4lk/specclaw
Path: plugins/specclaw-extras/skills/debug/SKILL.md
Versions recorded: 1
Latest version: git:20261011.0845a18, committed Oct 11, 2026
Size: 7,747 bytes
Repository stars: 14
License: MIT

Use when a bug, test failure, build failure, or unexpected behaviour is reported or observed, before proposing any fix.

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

# 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.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add chan4lk/specclaw/debug@sha256:609fec873b054558

The line at the top of this page pins the label git:20261011.0845a18, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_bjqaoms7gmuaea6f.svg)](https://markdownregistry.com/a/art_bjqaoms7gmuaea6f)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 11, 2026.

version	committed	commit	size	audit
git:20261011.0845a18 latest	2026-10-11	0845a18	7,747 B	B	view

Audit of the latest version

B 16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the 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 (7747 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

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

chan4lk/specclaw · 14 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_bjqaoms7gmuaea6f
GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/debug
GET https://markdownregistry.com/api/v1/blob/609fec873b054558e9e81b50354a769b4e166c5632bab817b17e2b3cdf81593b

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.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from chan4lk/specclaw

specclaw SKILL.md skill

chan4lk/specclaw · .agents/skills/specclaw/SKILL.md · Run the SpecClaw spec-driven lifecycle in this repository when a request needs proposal, planning, build, verification…

git:20261011.f968269 · audit A · 14 stars

CLAUDE.md CLAUDE.md file

chan4lk/specclaw · CLAUDE.md

git:20261029.e7b3be8 · audit A · 14 stars

llms-full.txt@docs llms.txt file

chan4lk/specclaw · docs/llms-full.txt

git:20261011.f968269 · audit A · 14 stars

llms.txt@docs llms.txt file

chan4lk/specclaw · docs/llms.txt

git:20260717.fc3814b · audit A · 14 stars

bf-analyze SKILL.md skill

chan4lk/specclaw · plugins/specclaw-bf/skills/bf-analyze/SKILL.md · Use when onboarding to an existing or legacy codebase that needs a grounded stack, dependency and risk report.