debug SKILL.md skillA

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

Install it, pinned
mdr add abdurrafay2004/handoff/debug@git:20260711.bfd3a58

Pins git:20260711.bfd3a58 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
abdurrafay2004/handoff
Path
skills/debug/SKILL.md
Versions recorded
5
Latest version
git:20260711.bfd3a58, committed Jul 11, 2026
First version recorded
Jul 2, 2026
Size
11,309 bytes
Repository stars
5
License
MIT

Use when encountering any bug, test failure, unexpected behavior, or performance regression — before proposing any fix. Root-cause discipline plus a feedback-loop method; applies at every tier.

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

Part of the **Build/Verify** phases — see the `workflow` skill for tiers and sequencing.

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

**The Iron Law: NO FIXES WITHOUT ROOT-CAUSE INVESTIGATION FIRST.**

Use for any technical issue — test failures, production bugs, unexpected behavior,
performance problems, build failures, integration issues. Especially when under
time pressure, when "just one quick fix" seems obvious, or when previous fixes
didn't work. Debugging discipline is tier-independent: a T1 bug still gets a root
cause (the process is fast for simple bugs).

## Phase 0 — Read the local context

Before exploring, read the nearest `CONTEXT.md` and `.handoff/` state if they
exist — a correct mental model of the modules involved beats an hour of tracing.

## Phase 1 — Build a feedback loop

**This is the skill; everything else is mechanical.** A **tight** pass/fail
signal that goes red on *this* bug is what bisection, hypotheses, and
instrumentation all consume. Without one, no amount of staring at code helps.
Spend disproportionate effort here.

Ways to construct one, roughly in order:
…

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_nlt4ayks3vs3swvp/c9749016fc010f6e1e94bb402e43846e1ca55b1f8cdd6a8a58aa20dab7f78ee9.json

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

The exact contents, by fingerprint
mdr add abdurrafay2004/handoff/debug@sha256:c9749016fc010f6e

The line at the top of this page pins the label git:20260711.bfd3a58, 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_nlt4ayks3vs3swvp.svg)](https://markdownregistry.com/a/art_nlt4ayks3vs3swvp)

2 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 abdurrafay2004/handoff/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 2, 2026 and Jul 11, 2026, about one every 2 days.

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

versioncommittedcommitsizeaudit
git:20260711.bfd3a58 latest2026-07-11 bfd3a58 11,309 BA view · diff
git:20260711.46a34002026-07-11 46a3400 11,315 BA view · diff
git:20260702.0ea7c432026-07-02 0ea7c43 11,159 BA view · diff
git:20260702.82cfccf2026-07-02 82cfccf 11,003 BA view · diff
git:20260702.4afacee2026-07-02 4afacee 9,723 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 (11309 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

abdurrafay2004/handoff · 5 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_nlt4ayks3vs3swvp
GET https://markdownregistry.com/api/v1/resolve?ref=abdurrafay2004/handoff/debug
GET https://markdownregistry.com/api/v1/blob/c9749016fc010f6e1e94bb402e43846e1ca55b1f8cdd6a8a58aa20dab7f78ee9

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 abdurrafay2004/handoff

AGENTS.md AGENTS.md file
abdurrafay2004/handoff · AGENTS.md
git:20261008.0e07558 · audit A · 5 stars
CLAUDE.md CLAUDE.md file
abdurrafay2004/handoff · CLAUDE.md
git:20261116.574db06 · audit A · 5 stars
architecture SKILL.md skill
abdurrafay2004/handoff · skills/architecture/SKILL.md · Scan the codebase for architectural friction and propose deepening opportunities as candidate cards, then interrogate…
git:20260711.bfd3a58 · audit A · 5 stars
brief SKILL.md skill
abdurrafay2004/handoff · skills/brief/SKILL.md · Use when starting a new feature or product request — clarifies scope and decisions before implementation. Supplies a…
git:20261008.f553434 · audit A · 5 stars
browser-qa SKILL.md skill
abdurrafay2004/handoff · skills/browser-qa/SKILL.md · Use to exercise the running app in a real browser — after UI changes, before ship, or when the user asks to QA the…
git:20261008.0e07558 · audit A · 5 stars
context-audit SKILL.md skill
abdurrafay2004/handoff · skills/context-audit/SKILL.md · Audit what loads into every session for this project — plugins, MCP servers, connectors, skills — find what the project…
git:20261116.574db06 · audit A · 5 stars
delegate SKILL.md skill
abdurrafay2004/handoff · skills/delegate/SKILL.md · Use when a task would flood the main context window — broad searches, verbose test/build output, 2+ independent…
git:20261008.0e07558 · audit A · 5 stars
design SKILL.md skill
abdurrafay2004/handoff · skills/design/SKILL.md · Use when designing or improving a module's interface, deciding where a seam goes, making code more testable or…
git:20260702.82cfccf · audit A · 5 stars
grill-me SKILL.md skill
abdurrafay2004/handoff · skills/grill-me/SKILL.md · Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of…
git:20260711.bfd3a58 · audit A · 5 stars
learn SKILL.md skill
abdurrafay2004/handoff · skills/learn/SKILL.md · Use at the end of T3 work, after an incident/rollback, or when the user asks for a retro — turns what happened into…
git:20260711.bfd3a58 · audit A · 5 stars
plan SKILL.md skill
abdurrafay2004/handoff · skills/plan/SKILL.md · Use when a task is T2/T3 — before building a feature that spans multiple files or carries risk. Produces an…
git:20261008.f553434 · audit A · 5 stars
security SKILL.md skill
abdurrafay2004/handoff · skills/security/SKILL.md · Use for a full security audit — T3 verify gate (money, auth, user data, migrations), pre-launch check, or when the user…
git:20261008.0e07558 · audit A · 5 stars

Every file in abdurrafay2004/handoff

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.