Diagnose root causes through a four-phase debugging workflow.
npx skills add https://github.com/mnsgrosa/skills --skill systematic-debugging-mnsgrosa
Please help me install this Agent Skill. Skill: systematic-debugging Source: https://github.com/mnsgrosa/skills/tree/main/skills/systematic-debugging Command: npx skills add https://github.com/mnsgrosa/skills --skill systematic-debugging-mnsgrosa
Systematic Debugging provides a disciplined, phase-driven approach to diagnose bugs, ensuring root causes are found before any fixes are attempted, reducing wasted time and rework.
Follow Phase 1 through Phase 4 in order before proposing any fixes.
High-intent search queries and answers about installing and using this skill.
Systematic root-cause debugging is a phased approach to identify the underlying origin of bugs before attempting fixes, preventing superficial symptom patches in complex multi-component systems. It enforces discipline through a four-phase workflow to reduce rework.
To debug test failures and production bugs without applying symptom fixes, follow a strict four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This ensures you verify the root cause before proposing any fixes.
Yes, you can use a phased debugging workflow for high-pressure scenarios and collaborative decision-making. It includes anti-pattern awareness and defense-in-depth practices to prevent shortcuts and ensure reliable, auditable resolutions under pressure.
The best way to trace root causes across multi-component technical issues is to enforce a structured workflow that isolates the root cause first. By applying pattern analysis and hypothesis testing, you prevent premature fixes and ensure reliable resolutions.
You should avoid shortcuts in debugging whenever facing complex production bugs or performance problems. Ad-hoc fixes often address only symptoms, leading to recurring failures; applying defense-in-depth practices prevents this and delivers auditable resolutions.
miptah21Diagnose failing Apache Airflow DAG runs and produce root-cause analyses.
MovchanetsDiagnose software errors by tracing stack traces to root causes.
ianphilMonitor tmux pane test output to drive the RED-GREEN-REFACTOR workflow.
drimchanskyGuide systematic reproduction, isolation, diagnosis, and verification of software bugs.
