skills.rest
venhdev
venhdevCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Enforce a 4-phase root cause investigation workflow for technical issues.

Updated May 3, 2026
Search Tags:#debugging#root cause analysis#defense-in-depth#systematic problem solving#bug resolution#test failure troubleshooting#production incident response
One-click install
npx skills add https://github.com/venhdev/skills --skill systematic-debugging-venhdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/venhdev/skills/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/venhdev/skills --skill systematic-debugging-venhdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random bug fixes waste time, create new bugs, and mask underlying issues, especially under time pressure when quick symptom patches seem tempting but lead to recurring problems and longer resolution times overall.

Core Features & Use Cases

  • 4-Phase Systematic Workflow: Mandatory root cause investigation, pattern analysis, hypothesis testing, and controlled implementation to ensure permanent fixes.
  • Pressure-Resistant Guardrails: Explicit "iron law" against fixes without root cause investigation, anti-pattern guidance, and rationalization checklists to prevent shortcutting during emergencies or when exhausted.
  • Supporting Techniques: Built-in guidance for root cause tracing through call stacks, defense-in-depth validation, and condition-based waiting to address common debugging challenges.
  • Use Case: Ideal for production outages, flaky tests, multi-component system failures, and any scenario where quick fixes would cause more harm than good.

Quick Start

Use the systematic-debugging skill to investigate the root cause of the failing payment processing test before proposing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I debug a production incident systematically instead of just patching symptoms?▼

Debug production incidents systematically by enforcing a mandatory 4-phase root cause investigation workflow with guardrails against rationalization and shotgun fixes to ensure permanent resolution.

What is root cause analysis in software debugging and when should I apply it?▼

Root cause analysis in software debugging is a mandatory investigation process to find the underlying origin of failures. Apply it during production outages, flaky tests, and multi-component system failures to prevent recurring bugs.

How do I troubleshoot flaky test failures and multi-component integration errors?▼

Troubleshoot flaky test failures and integration errors using pattern analysis, hypothesis testing, and controlled implementation within a 4-phase workflow that traces root causes through call stacks and validates defense-in-depth.

What's the best way to avoid shotgun fixes and shortcutting during urgent bug resolution?▼

Avoid shotgun fixes during urgent bug resolution by applying pressure-resistant guardrails, an explicit iron law against unrooted fixes, and rationalization checklists to enforce systematic problem solving under time pressure.

Does systematic debugging work for performance degradation and integration errors?▼

Yes, systematic debugging works for performance degradation and integration errors by applying condition-based waiting, call stack tracing, and defense-in-depth validation to ensure fixes address root causes across all software development scenarios.

Related Skills

Explore More Software Engineering Skills→
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
hitsumabushi334hitsumabushi334

systematic-debugging

Guide engineers through a four-phase root cause debugging process.

Community
Advanced
summarybotngsummarybotng
2

observability-testing-patterns

Validate dashboards, alert rules, logs, traces, and SLO compliance.

Official
Advanced
JBonfimJBonfim

no-workarounds

Enforce root-cause fixes over workarounds in software engineering tasks.

Community
Advanced