medharness: Skill for Claude Code

.claude/skills/systematic-debugging/SKILL.md

systematic-debugging is a skill for Claude Code from charliehzm/medharness. It costs 151 tokens per session (726 once invoked), scanned A, original, Apache-2.0.

A structured method for investigating software bugs and failed tests. It moves from the symptom to a small reproduction, the underlying cause, a fix, and a regression test.

In plain words
What is it for?
Use it when tests fail, a code review finds a defect, or a bug is reported. It helps narrow the failing input, test one explanation at a time, fix the root cause, and add coverage for the failure.
Why use it?
It reduces trial-and-error patches that hide the real problem or let it return later. The written debug record also preserves what was learned.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is charliehzm/medharness's own configuration. It tells Claude Code how to work on medharness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything medharness configures →

Reuse

Borrowing it

Nothing to install: this file belongs to charliehzm/medharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/charliehzm/medharness/main/.claude/skills/systematic-debugging/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/charliehzm/medharness

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for systematic-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/charliehzm/medharness/systematic-debugging.svg)](https://agentmods.dev/skills/charliehzm/medharness/systematic-debugging)
Your own site
<a href="https://agentmods.dev/skills/charliehzm/medharness/systematic-debugging"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/systematic-debugging.svg" alt="Measured on agentmods" height="20"></a>
Per session 151 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 726 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00151 $0.00726
Opus 5 $0.00076 $0.00363
Sonnet 5 $0.00030 $0.00145
Haiku 4.5 $0.00015 $0.00073

Measured 7d ago against content hash 5947435b09fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

systematic-debugging scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/systematic-debugging/SKILL.md · 72 lines

What it actually says

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

Anti What it looks like Cost
Try-this-try-that "let me change X and rerun" hours wasted, no learning
Symptom patch catch + log + return bug returns elsewhere
Print debugging at scale scattered prints, none removed noise, audit hits
Fix without test regression returns infinite 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".
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 72 lines · 151 tokens per session scan A 5947435b09fc

Subscribe to this mod's changes

systematic-debugging is a skill published in the GitHub repository charliehzm/medharness (86 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 151 tokens to every session and 726 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

HIPAA Compliance Testing

Testing HIPAA compliance for healthcare applications including PHI handling, audit logging, access controls, and data encryption verification.

PramodDutta/qaskills · 28 tokens

agent-debug-fixer

中文调试修复技能。用于报错、测试失败、页面异常、功能不符合预期、需要定位根因并做最小修复时。触发语包括"进入调试模式""帮我修问题""报错了""测试失败""页面坏了""找根因"。.

hashgraph-online/awesome-codex-plugins · 71 tokens

om-troubleshooter

Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.

open-mercato/open-mercato · 73 tokens

moai-workflow-loop

Ralph Engine - Automated feedback loop with LSP diagnostics and AST-grep integration for continuous code quality improvement. Use when implementing error-driven development, automated fixing, or continuous quality validation workflows.

modu-ai/moai-adk · 44 tokens

moai-workflow-testing

Use when writing tests, measuring coverage, or running characterization, performance, or PR-review QA. Comprehensive specialist combining DDD testing, characterization tests, performance profiling, and TRUST 5 quality-assurance validation.

modu-ai/moai-adk · 47 tokens

confirm-failures-are-causally-linked-to-the-task-before-reportin

When delegating a task affected by this skill, include.

ZaxbyHub/opencode-swarm · 29 tokens