Agent skill · operations · aaaaqwq
Systematic Debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Why this skill is useful
Provides a systematic framework for debugging that includes specific investigative steps and diagnostic scripts not commonly known.
What it needs
About 6k tokens when loaded. Last updated 2026-08-06. 83 stars on the source repository.
What this skill does
Systematic Debugging Overview Random fixes waste time and create new bugs. Quick patches mask underlying issues. Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure. Violating the letter of this process is violating the spirit of debugging. The Iron Law If you haven't completed Phase 1, you cannot propose fixes. When to Use Use for ANY technical issue: Test failures Bugs in production Unexpected behavior Performance problems Build failures Integration issues Use this ESPECIALLY when: Under time pressure (emergencies make guessing tempting) "Just one quick fix" seems obvious You've already tried multiple fixes Previous fix didn't work You don't fully understand the issue Don't skip when: Issue seems simple (simple bugs have root causes too) You're in a hurry (rushing guarantees rework) Manager wants it fixed NOW (systematic is faster than thrashing) The Four Phases You MUST complete each phase before proceeding to the next. Phase 1: Root Cause Investigation BEFORE attempting ANY fix: 1. Read Error Messages Carefully Don't skip past errors or warnings They often contain the exact solution Read stack traces completely Note line numbers, file paths, error codes 2. Reproduce Consistently Can you trigger it reliably? What are the exact steps? Does it happen every time? If not reproducible → gather more data, don't guess 3. Check Recent Changes What changed that could cause this? Git diff, recent commits New dependencies, config changes Environmental differences 4. Gather Evidence in Multi-Component Systems WHEN system has multiple components (CI → build → signing, API → service → database): BEFORE proposing fixes, add diagnostic instrumentation: Example (multi-layer system): This reveals: Which layer fails (secrets → workflow ✓, workflow → build ✗) 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aaaaqwq/sp-systematic-debugging