agentleFS
charliehzmcharliehzm/medharness/.claude/skills/systematic-debugging/SKILL.md

systematic-debugging

Skill85 starsChanged 6 months agoApache-2.0View on GitHub

Use this skill whenever a test fails, a code review surfaces a defect, or a bug is reported, to perform structured root-cause analysis rather than trial-and-error patches. Walks symptom → narrow → reproduce → minimal repro → root cause → fix → regression test. Outputs a debug log entry that feeds into Memory and AUDIT_BUNDLE. Chinese trigger examples: "调试", "找 bug 根因", "系统化调试", "Bug 定位", "test failure 调试", "review 反馈 修复". Do NOT use for stylistic feedback (just fix), do NOT use for known one-line fixes. Success = root cause identified with evidence, fix applied at root cause level, regression test added.

190 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • mjunaidcaSkill

    building-chatgpt-apps

    Guides creation of ChatGPT Apps with interactive widgets using OpenAI Apps SDK and MCP servers. Use when building ChatGPT custom apps with visual UI components, embedded widgets, or rich interactive experiences. Covers widget architecture, MCP server setup with FastMCP, response metadata, and Developer Mode configuration. NOT when building standard MCP servers without widgets (use building-mcp-servers skill instead).

    Also in 4 projects that use this

  • mjunaidcaSkill

    building-chat-interfaces

    Build AI chat interfaces with custom backends, authentication, and context injection. Use when integrating chat UI with AI agents, adding auth to chat, injecting user/page context, or implementing httpOnly cookie proxies. Covers ChatKitServer, useChatKit, and MCP auth patterns. NOT when building simple chatbots without persistence or custom agent integration.

    Also in 4 projects that use this

  • +2 more from Leodorareluctant259
  • +4 more from mjunaidca

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add regression test that exercises the minimal reproducer.

    line 59
  2. Very specific:

    Write DEBUG_LOG entry: symptom + reproducer + root cause + fix + test ref.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 177 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Systematic Debugging

Stops the "patch the symptom, ship, repeat" anti-pattern.

The cycle

Symptom
  ↓ narrow (which input class / which code path)
Reproducer (smallest input that triggers it)
  ↓ instrument (log / trace / debugger)
Hypothesis (1 falsifiable claim)
  ↓ test the hypothesis directly
Root cause (the WHY behind the WHAT)
  ↓ fix at root (not symptom)
Regression test (locks behavior)

Anti-patterns

AntiWhat it looks likeCost
Try-this-try-that"let me change X and rerun"hours wasted, no learning
Symptom patchcatch + log + returnbug returns elsewhere
Print debugging at scalescattered prints, none removednoise, audit hits
Fix without testregression returnsinfinite loop

Workflow

  1. Capture the failure clearly (test name + error + line).
  2. Narrow input class — what's special about the failing case?
  3. Build a minimal reproducer (independent of the test suite).
  4. Form ONE hypothesis. Test it. If wrong, revise.
  5. Identify root cause; trace back to design / spec / data invariant.
  6. Apply fix at root.
  7. Add regression test that exercises the minimal reproducer.
  8. Write DEBUG_LOG entry: symptom + reproducer + root cause + fix + test ref.

Integration

  • Triggered by: test failure (Step 9), review feedback (Step 8), bug report, compliance gap (Step 10 → Step 11)
  • Output: DEBUG_LOG entries inform memory-curate (Phase 3 inference rederive) and audit-snapshot (prompts/debug_log/)

Common failure modes

  1. Hypothesis = "it should work" — not falsifiable. Mitigation: every hypothesis must predict an observable.
  2. Fix without regression test — the bug will return. Mitigation: discipline; reject the diff otherwise.
  3. Fix at the wrong layer — patches caller when bug is in callee's invariant. Mitigation: ask "why did the invariant break".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.