Debugging

Name: Debugging
Author: tstapler

ASecurity

Systematic debugging frameworks for finding and fixing bugs - includes

8 stars

0 votes

0 copies

0 views

Added 9/20/2026

testingtestingdebugging

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add tstapler/dotfiles --skill debugging --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Debugging?

Add the live security badge to your README — it updates automatically with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tstapler-debugging/badge)](https://www.skillsdirectory.com/skills/tstapler-debugging)

More formats (shields.io, HTML) on the badges page.

Download Zip

Files

SKILL.md

---
name: debugging
description: Systematic debugging frameworks for finding and fixing bugs - includes
  root cause analysis, defense-in-depth validation, and verification protocols
---

# 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

| Symptom | Sub-Skill |
|---------|-----------|
| Test failure, unexpected behavior | systematic-debugging |
| Error appears in wrong location | root-cause-tracing |
| Same bug keeps recurring | defense-in-depth |
| Need to confirm fix works | verification-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%

Attribution

tstapler

View source More from tstapler →

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- name: debugging description: Systematic debugging frameworks for finding and fixing bugs - includes root cause analysis, defense-in-depth validation, and verification protocols --- # 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 | Symptom | Sub-Skill | |---------|-----------| | Test failure, unexpected behavior | systematic-debugging | | Error appears in wrong location | root-cause-tracing | | Same bug keeps recurring | defense-in-depth | | Need to confirm fix works | verification-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%