Agent skill · software engineering · samhvw8
debugging
Systematic debugging methodology with root cause analysis. Phases: investigate, hypothesize, validate, verify. Capabilities: backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention. Actions: debug, investigate, trace, analyze, validate, verify bugs. Keywords: debugging, root cause, bug fix, stack trace, error investigation, test failure, exception handling, breakpoint, logging, reproduce, isolate, regression, call stack, symptom vs cause, hypothesis testing, validation, verification protocol. Use when: encountering bugs, analyzing test failures, tracing unexpected behavior, investigating performance issues, preventing regressions, validating fixes before completion claims.
Why this skill is useful
Adds a systematic debugging methodology with specific phases and techniques that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2025-12-09. 10 stars on the source repository.
What this skill does
Debugging Comprehensive debugging framework combining systematic investigation, root cause tracing, defense-in-depth validation, and verification protocols. Core Principle NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST Random fixes waste time and create new bugs. Find the root cause, fix at source, validate at every layer, verify before claiming success. When to Use Always use for: Test failures, bugs, unexpected behavior, performance issues, build failures, integration problems, before claiming work complete Especially when: Under time pressure, "quick fix" seems obvious, tried multiple fixes, don't fully understand issue, about to claim success The Four Techniques 1. Systematic Debugging (references/systematic-debugging.md) Four-phase framework ensuring proper investigation: Phase 1: Root Cause Investigation (read errors, reproduce, check changes, gather evidence) Phase 2: Pattern Analysis (find working examples, compare, identify differences) Phase 3: Hypothesis and Testing (form theory, test minimally, verify) Phase 4: Implementation (create test, fix once, verify) Key rule: Complete each phase before proceeding. No fixes without Phase 1. Load when: Any bug/issue requiring investigation and fix 2. Root Cause Tracing (references/root-cause-tracing.md) Trace bugs backward through call stack to find original trigger. Technique: When error appears deep in execution, trace backward level-by-level until finding source where invalid data originated. Fix at source, not at symptom. Includes: scripts/find-polluter.sh for bisecting test pollution Load when: Error deep in call stack, unclear where invalid data originated 3. Defense-in-Depth (references/defense-in-depth.md) Validate at every layer data passes through. Make bugs impossible. Four layers: Entry validation → Business logic → Environment guards → Debug instrumentation Load when: After finding root cause, need to add comprehensive validation 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills samhvw8/debugging