mcpField
D
debugging

debugging

github.com/mrgoonieTesting & quality2.2k573 installsUpdated 30w ago
Repository

About debugging

A set of debugging skills for software developers and agents, covering root-cause investigation, tracing, layered validation, and verification before reporting completion.

Key features

  1. 01Four-phase systematic debugging
  2. 02Trace causes through call stacks
  3. 03Validate across data layers
  4. 04Verify before claiming completion

Use cases

  1. 01Investigate test failures or unexpected behavior
  2. 02Locate errors deep in a call stack
  3. 03Prevent recurring bugs
  4. 04Confirm a fix before reporting it

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mrgoonie/claudekit-skills --skill debugging

After installing, type/debuggingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

root-cause-tracing/
find-polluter.sh
systematic-debugging/
CREATION-LOG.md
test-academic.md
test-pressure-1.md
test-pressure-2.md
test-pressure-3.md

Details

From the project README

Debugging Skills

A collection of systematic debugging methodologies that ensure thorough investigation before attempting fixes.

Available Sub-Skills

Systematic Debugging

Location: systematic-debugging/SKILL.md

Four-phase debugging framework: Root Cause Investigation → Pattern Analysis → Hypothesis Testing → Implementation. The iron law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.

Root Cause Tracing

Location: root-cause-tracing/SKILL.md

Trace bugs backward through the call stack to find the original trigger. Don't fix symptoms - find where invalid data originated and fix at the source.

Defense-in-Depth Validation

Location: defense-in-depth/SKILL.md

Validate at every layer data passes through to make bugs structurally impossible. Four layers: Entry Point → Business Logic → Environment Guards → Debug Instrumentation.

Verification Before Completion

Location: verification-before-completion/SKILL.md

Run verification commands and confirm output before claiming success. The iron law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.

When to Use

  • Bug in production → Start with systematic-debugging
  • Error deep in stack trace → Use root-cause-tracing
  • Fixing a bug → Apply defense-in-depth after finding root cause
  • About to claim "done" → Use verification-before-completion

Quick Dispatch

SymptomSub-Skill
Test failure, unexpected behaviorsystematic-debugging
Error appears in wrong locationroot-cause-tracing
Same bug keeps recurringdefense-in-depth
Need to confirm fix worksverification-before-completion

Core Philosophy

"Systematic debugging is FASTER than guess-and-check thrashing."

From real debugging sessions:

  • Systematic approach: 15-30 minutes to fix
  • Random fixes approach: 2-3 hours of thrashing
  • First-time fix rate: 95% vs 40%

Comments

Markdown supported