debugging

Savant verdict: Review advised

Security analysis or source-hub review identified patterns requiring attention.

Live evaluation

Not evaluated yet. Workspaces can request a live evaluation.

Security assessment

Scan pending.

Structure

• Ships 1 executable scriptroot-cause-tracing/find-polluter.sh. Review what they do before enabling the skill for agents with tool access.
• No license declaredConfirm you may reuse this skill before importing it into your repository.
• The source hub's security checks flagged this skillGen Agent Trust Hub: warn (The skill utilizes coercive language and persona-based threats to enforce compliance, and it includes debugging patterns that expose sensitive environment and keychain data. It also presents an indirect prompt injection risk through its reliance on processing external log and diff data.); Runlayer: warn (10/11 files flagged); ZeroLeaks: warn (Scan incomplete)

SKILL.md

---
name: debugging
description: Systematic debugging frameworks for finding and fixing bugs - includes root cause analysis, defense-in-depth validation, and verification protocols
when_to_use: when encountering bugs, test failures, unexpected behavior, or needing to validate fixes before claiming completion
version: 1.0.0
languages: all
---

# 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%