debug SKILL.md skillA

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

Install it, pinned
mdr add nyelonong/galdr/debug@git:20261114.fa8b3c3

Pins git:20261114.fa8b3c3 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
nyelonong/galdr
Path
skills/debug/SKILL.md
Versions recorded
5
Latest version
git:20261114.fa8b3c3, committed Nov 14, 2026
First version recorded
Jul 19, 2026
Size
2,535 bytes
Repository stars
13
License
MIT

Use when you diagnose a bug, a flaky test, unexpected behavior or a production incident, before you propose or write a 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

# Debug

NO FIXES WITHOUT ROOT CAUSE.

This is a hard rule. A fix without a root cause is a guess that changed the symptom. If
you want to change code to remove a bug and you cannot state its root cause, stop.

## Do not

- Do not change code as a fix before a repro exists. A repro shows the bug on demand.
- Do not claim a behavior (what happens, when, how often) without the exact command and
  its output in the same message.
- Do not try a fourth fix at a site where three fixes failed. The defect is upstream.
  Go back to the design.
- Do not close a production incident without an open root-cause item. The item names an
  owner and a next step. Mitigation is never the end.

## Make a repro first

Before you make a theory, build a repro. A repro is a command whose output changes with
the hypothesis that is true. Use the cheapest one that separates the hypotheses, for
example a failing test, `curl`, a log search or `git bisect`. Run a subagent's claim
about the bug again before you repeat it.

## Hypotheses

Write each hypothesis when you make it, in the plan file or in the report:

```
HYP <n>: <hypothesis> → <experiment> → <result>
```
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jvryfztgbdjzelkp/9a88a8880108c9ac747921f2e91bc7e77565ad26cb5d652e92b3abfe9c302b30.json

Then /plugin install debug@markdownregistry-jvryfztgbdjzelkp in Claude Code. It installs git:20261114.fa8b3c3, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add nyelonong/galdr/debug@sha256:9a88a8880108c9ac

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

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

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

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in nyelonong/galdr/debug since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of debug from somewhere else? Ask it: where did my debug come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between Jul 19, 2026 and Nov 14, 2026, about one every 30 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261114.fa8b3c3 latest2026-11-14 fa8b3c3 2,535 BA view · diff
git:20261114.052ab812026-11-14 052ab81 2,475 BA view · diff
git:20261114.9c4bffb2026-11-14 9c4bffb 2,597 BA view · diff
git:20260725.66b7da82026-07-25 66b7da8 5,714 BA view · diff
git:20260719.b390e912026-07-19 b390e91 5,702 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (2535 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

nyelonong/galdr · 13 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_jvryfztgbdjzelkp
GET https://markdownregistry.com/api/v1/resolve?ref=nyelonong/galdr/debug
GET https://markdownregistry.com/api/v1/blob/9a88a8880108c9ac747921f2e91bc7e77565ad26cb5d652e92b3abfe9c302b30

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 nyelonong/galdr

galdr SKILL.md skill
nyelonong/galdr · skills/galdr/SKILL.md · Use when the user runs /galdr to start or continue a piece of engineering work, or asks which galdr flow fits a request.
git:20261119.142bf5e · audit A · 13 stars
handoff SKILL.md skill
nyelonong/galdr · skills/handoff/SKILL.md · Use when the user runs /galdr:handoff to pass work to a new session, a worker or reviewer session, or the session of…
git:20261114.0740ff1 · audit A · 13 stars
prove SKILL.md skill
nyelonong/galdr · skills/prove/SKILL.md · Use before you change production code, before you claim that work is complete, or when you audit a document against…
git:20261115.1faad52 · audit A · 13 stars
review SKILL.md skill
nyelonong/galdr · skills/review/SKILL.md · Use when the user runs /galdr:review to review a branch, diff or plan document, or asks for browser approval.
git:20261115.1faad52 · audit A · 13 stars
shape SKILL.md skill
nyelonong/galdr · skills/shape/SKILL.md · Use when the user runs /galdr:shape to turn an idea, a position to test, or clear requirements into the goal and…
git:20261114.0740ff1 · audit A · 13 stars

Every file in nyelonong/galdr

Other files named debug

debug SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/debug/SKILL.md · Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
git:20260925.570ed1c · audit A · 40,827 stars
debug SKILL.md skill
nanocoai/nanoclaw · .claude/skills/debug/SKILL.md · Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to…
git:20261022.0474572 · audit B · 31,124 stars
debug SKILL.md skill
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…
v1.0 · audit A · 1,052 stars
debug SKILL.md skill
suboss87/fdeops · skills/debug/SKILL.md · Investigate a failure, regression or incorrect result in an integration or application, even before it can be…
git:20261005.ed7f271 · audit A · 817 stars
debug SKILL.md skill
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…
git:20261109.ba0e80d · audit A · 608 stars
debug SKILL.md skill
rsmdt/the-startup · plugins/start/skills/debug/SKILL.md · Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
git:20261011.48bd3ee · audit A · 582 stars
debug SKILL.md skill
vibeeval/vibecosystem · skills/debug/SKILL.md · Investigate a reported failure through relevant logs, code, state, and history without editing the implementation.
git:20261104.1844d11 · audit A · 552 stars
debug SKILL.md skill
me2resh/apexyard · .claude/skills/debug/SKILL.md · Hypothesis-driven debugging — architecture-first reading + evidence-before-fix. For bugs that resisted naïve fix…
git:20261015.37f5689 · audit A · 551 stars

Browse by kind, by grade A, or by owner.