systematic-debugging SKILL.md skillA

systematic-debugging from innei/ryugi is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add innei/ryugi/systematic-debugging@git:20261112.7f08ac0

Pins git:20261112.7f08ac0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
innei/ryugi
Path
skills/systematic-debugging/SKILL.md
Versions recorded
5
Latest version
git:20261112.7f08ac0, committed Nov 12, 2026
First version recorded
Oct 19, 2026
Size
8,526 bytes
Repository stars
524
License
a license file GitHub does not identify

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

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

# Systematic Debugging

## Overview

**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure.

**Violating the letter of this process is violating the spirit of debugging.**

## The Iron Law

```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```

If you haven't completed Phase 1, you cannot propose fixes.

## When to Use

Any technical issue: test failures, production bugs, unexpected behavior,
performance problems, build failures, integration issues.

Especially under time pressure, when "one quick fix" seems obvious, when a
previous fix didn't work, or when the issue seems too simple to need it.
Simple bugs have root causes too, and systematic is faster than thrashing.

## The Four Phases

You MUST complete each phase before proceeding to the next.

### Phase 1: Root Cause Investigation

**BEFORE attempting ANY fix:**

1. **Read Error Messages Carefully**
   - Don't skip past errors or warnings; they often contain the exact solution
   - Read stack traces completely: line numbers, file paths, error codes

2. **Reproduce Consistently**
   - Exact steps, and whether it happens every time
…

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_ee6jnwjf73d5tkqp/5034ce53990b82e3544d6344548b5f6130302f422ed936999eca4b6d6fac2e12.json

Then /plugin install systematic-debugging@markdownregistry-ee6jnwjf73d5tkqp in Claude Code. It installs git:20261112.7f08ac0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add innei/ryugi/systematic-debugging@sha256:5034ce53990b82e3

The line at the top of this page pins the label git:20261112.7f08ac0, 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_ee6jnwjf73d5tkqp.svg)](https://markdownregistry.com/a/art_ee6jnwjf73d5tkqp)

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 innei/ryugi/systematic-debugging 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 systematic-debugging from somewhere else? Ask it: where did my systematic-debugging 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 Oct 19, 2026 and Nov 12, 2026, about one every 6 days.

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

versioncommittedcommitsizeaudit
git:20261112.7f08ac0 latest2026-11-12 7f08ac0 8,526 BA view · diff
git:20261111.7393ad32026-11-11 7393ad3 10,549 BA view · diff
git:20261027.20888332026-10-27 2088833 10,502 BA view · diff
git:20261021.b62642c2026-10-21 b62642c 9,872 BA view · diff
git:20261019.2c789cd2026-10-19 2c789cd 9,499 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 (8526 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

innei/ryugi · 524 stars · license a license file GitHub does not identify · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ee6jnwjf73d5tkqp
GET https://markdownregistry.com/api/v1/resolve?ref=innei/ryugi/systematic-debugging
GET https://markdownregistry.com/api/v1/blob/5034ce53990b82e3544d6344548b5f6130302f422ed936999eca4b6d6fac2e12

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 innei/ryugi

writing-skills SKILL.md skill
innei/ryugi · .claude/skills/writing-skills/SKILL.md · Use when creating new skills, editing existing skills, or verifying skills work before deployment
git:20261027.2088833 · audit A · 524 stars
AGENTS.md AGENTS.md file
innei/ryugi · AGENTS.md
git:20261117.27b21bf · audit A · 524 stars
artifacts SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-artifacts-single-entry-full/inputs/baseline-skill/SKILL.md · Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click…
git:20261113.586f356 · audit A · 524 stars
artifacts SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-artifacts-single-entry-full/inputs/candidate-skill/SKILL.md · Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click…
git:20261113.586f356 · audit A · 524 stars
artifacts SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-artifacts-slim/skills/baseline/SKILL.md · Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click…
git:20261112.aa9f450 · audit A · 524 stars
artifacts SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-artifacts-slim/skills/candidate/SKILL.md · Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click…
git:20261112.aa9f450 · audit A · 524 stars
brainstorming SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-brainstorming-slim/skills/baseline/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, modifying…
git:20261112.baa5cf8 · audit A · 524 stars
brainstorming SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-brainstorming-slim/skills/candidate/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, modifying…
git:20261112.baa5cf8 · audit A · 524 stars
executing-specs SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-executing-specs-slim/skills/baseline/SKILL.md · Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or…
git:20261112.e34ce62 · audit A · 524 stars
executing-specs SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-executing-specs-slim/skills/candidate/SKILL.md · Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or…
git:20261112.e34ce62 · audit A · 524 stars
systematic-debugging SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-systematic-debugging-slim/skills/baseline/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
git:20261112.7f08ac0 · audit A · 524 stars
systematic-debugging SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-systematic-debugging-slim/skills/candidate/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
git:20261112.7f08ac0 · audit A · 524 stars

Every file in innei/ryugi

Other files named systematic-debugging

systematic-debugging SKILL.md skill
obra/superpowers · skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
git:20261010.bb92a77 · audit A · 319,649 stars
systematic-debugging SKILL.md skill
mvschwarz/openrig · skills/_canonical/process/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
git:20261025.a37e271 · audit A · 8,889 stars
systematic-debugging SKILL.md skill
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
git:20261025.a37e271 · audit A · 8,889 stars
systematic-debugging SKILL.md skill
jnmetacode/superpowers-zh · skills/systematic-debugging/SKILL.md · 遇到任何 bug、测试失败或异常行为时使用,在提出修复方案之前执行
v1.9.1 · audit A · 8,551 stars
systematic-debugging SKILL.md skill
cbrock84/headcount · plugins/technology/skills/systematic-debugging/SKILL.md · Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever…
git:20260901.aa45383 · audit A · 2,543 stars
systematic-debugging SKILL.md skill
a5c-ai/babysitter · library/methodologies/superpowers/skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause…
git:20260601.da7723a · audit A · 1,914 stars
systematic-debugging SKILL.md skill
a5c-ai/babysitter · library/methodologies/rpikit/skills/systematic-debugging/SKILL.md · Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and…
git:20260605.09bdbf7 · audit A · 1,914 stars
systematic-debugging SKILL.md skill
ganyuanran/aegis · skills/systematic-debugging/SKILL.md · Use when encountering a bug, test failure, or unexpected behavior, before proposing fixes
git:20261025.21787f7 · audit A · 1,442 stars

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