debugging SKILL.md skillA
debugging from calebnewtonusc/chewbacca is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add calebnewtonusc/chewbacca/debugging@git:20260921.84800caPins git:20260921.84800ca in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- calebnewtonusc/chewbacca
- Path
skills/debugging/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260921.84800ca, committed Sep 21, 2026
- First version recorded
- Sep 16, 2026
- Size
- 2,972 bytes
- Repository stars
- 9
- License
- MIT
Find the root cause of a bug instead of guessing at it. Use when the user reports something broken, pastes an error or a stack trace, says this used to work, asks why is this happening, why is this failing, or what is wrong with this. Also use to trace how data flows through a codebase, follow a request end to end, or find where a value is being lost or changed. Also fires on: stack trace, traceback, exception, crash, crashed, segfault, null pointer, undefined, regression, reproduce, bisect…
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
# Debugging The protocol exists because the failure mode is universal: changing several things at once, then not knowing which one helped. ## The order, and do not skip **1. Read the error exactly.** Every word. `undefined` and `null` are different bugs with different causes. "Cannot read property x of undefined" names the property and that is usually the whole answer. **2. Go to the file and line in the trace before doing anything else.** Not a grep for something similar. The actual frame. If there is no stack trace, get one before theorizing; a bug report without one is a rumor. **3. Check the assumption.** Print the variable. Is it the shape you believed? Most bugs are a value being a different type, a different case, or absent, and are invisible to reasoning about the code because the code reads correctly. **4. Search the exact message.** Framework, exact string, year. Someone has hit it. **5. Check for a breaking change.** Read the migration guide for the version actually installed, not the version remembered. **6. `git diff` against the last working state.** The bug lives in the diff. This step alone solves most "it used to work" reports and it is the one most often …
Read the whole file at its exact version.
How to install
mdr add calebnewtonusc/chewbacca/debugging@sha256:583d01c7b4f4bec4The line at the top of this page pins the label git:20260921.84800ca, 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.
[](https://markdownregistry.com/a/art_ejjbvdtmxmczfsbm)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 16, 2026 and Sep 21, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.84800ca latest | 2026-09-21 | 84800ca | 2,972 B | A | view · diff |
| git:20260916.65678eb | 2026-09-16 | 65678eb | 2,806 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2972 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
calebnewtonusc/chewbacca · 9 stars · license MIT · pushed 2026-10-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ejjbvdtmxmczfsbm GET https://markdownregistry.com/api/v1/resolve?ref=calebnewtonusc/chewbacca/debugging GET https://markdownregistry.com/api/v1/blob/583d01c7b4f4bec485e01ec9336bc11c5a1cbdddb096875b589011c2d38f02ad
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 calebnewtonusc/chewbacca
Every file in calebnewtonusc/chewbacca