skills.rest
daviddatuX25
daviddatuX25COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnoses root causes of bugs and flaky tests via a four-phase framework.

Updated Feb 17, 2026
Search Tags:#testing#debugging#defense-in-depth#tracing#root-cause-analysis#phase-based#systematic-process
One-click install
npx skills add https://github.com/daviddatuX25/SecureCAT-v2 --skill systematic-debugging-daviddatux25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/daviddatuX25/SecureCAT-v2/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/daviddatuX25/SecureCAT-v2 --skill systematic-debugging-daviddatux25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a rigorous framework to diagnose and eliminate root causes of bugs and flaky tests before proposing fixes, avoiding symptom patches.

Core Features & Use Cases

  • Four-phase workflow (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) with explicit guardrails
  • Anti-patterns and defense-in-depth: STOP, re-analyze, never fix symptoms
  • Useful for production bugs, test failures, race conditions, and complex integration issues
  • Built-in escalation to add stack tracing and instrumentation for post-mortems

Quick Start

Load the skill and start with Phase 1: Root Cause Investigation to gather evidence before proposing any fixes.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to systematically find the root cause of a bug before fixing it?▼

Root cause analysis for flaky tests and production bugs uses a four-phase systematic debugging framework to gather evidence, analyze patterns, and test hypotheses before implementing fixes, avoiding symptom patches.

How do I debug flaky tests and race conditions without taking time-pressure shortcuts?▼

Debug flaky tests using a phase-based systematic process with built-in guardrails and anti-patterns that enforce evidence gathering and pattern analysis, resisting time-pressure shortcuts to prevent symptom patching.

When should I add stack tracing and instrumentation for a production bug post-mortem?▼

Add stack tracing and instrumentation during root cause investigation when initial evidence is insufficient, escalating complex production bugs and integration issues to gather precise diagnostic data for post-mortems.

Does systematic debugging work for complex integration issues and deployment workflow failures?▼

Yes, systematic debugging applies to any technical issue across code, tests, and deployment workflows, diagnosing complex integration problems and production bugs through structured pattern analysis and hypothesis testing.

What are the limitations of fixing symptoms instead of performing root cause analysis?▼

Fixing symptoms without root cause analysis leads to recurring bugs; systematic debugging enforces a STOP mechanism and defense-in-depth anti-patterns to re-analyze issues and ensure actual root causes are eliminated.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
mliudevmliudev

systematic-debugging

Trace bugs backward from evidence to validated root causes.

Community
Advanced
xlelibertyxleliberty

systematic-debugging

Identify and resolve technical issues through a four-phase debugging framework.

Community
Advanced