Investigate and confirm root cause before applying fixes.
npx skills add https://github.com/brmatola/gremlins --skill systematic-debugging-brmatola
Please help me install this Agent Skill. Skill: systematic-debugging Source: https://github.com/brmatola/gremlins/tree/main/skills/systematic-debugging Command: npx skills add https://github.com/brmatola/gremlins --skill systematic-debugging-brmatola
## What problem does it solve?
Systematic Debugging provides a disciplined approach to diagnosing software issues, ensuring you identify the root cause before attempting fixes, avoiding symptom-based patches that create new problems.
## Core Features & Use Cases
### Quick Start
Describe the failing behavior, reproduce it, gather evidence, then follow the four phases to identify and fix the root cause.
High-intent search queries and answers about installing and using this skill.
Root cause debugging requires reproducing the issue, gathering diagnostic evidence, and testing a single hypothesis with minimal changes before applying fixes. This structured approach prevents symptom-based patches that introduce new problems.
Debugging flaky tests and production bugs systematically involves a four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation. This enforces evidence gathering and reproducible steps to verify fixes.
Reproducing an integration failure requires describing the failing behavior, tracing data flow across components, and collecting logs. This evidence forms the basis for hypothesis-driven fixes during the root cause investigation phase.
Hypothesis testing when diagnosing software issues ensures you form a single hypothesis, test minimally, and verify results before proceeding. This prevents compounding errors and confirms the root cause before implementation.
Systematic debugging applies to performance problems, test failures, production issues, and integration failures. It guides structured evidence gathering and hypothesis testing across these scenarios to identify and verify root causes.
If a bug fix is not working, return to root cause investigation to verify reproducible steps and diagnostic instrumentation. Ensure your single hypothesis was tested with minimal changes before proceeding to implementation.
derHakenTrace data flow and apply a four-phase process to fix root causes.
yun520-1Guides users through a four-phase debugging process to identify root causes of technical issues.
vadimcomanescuGuide engineers through a four-phase debugging workflow from root-cause investigation to verification.
getspurEnforce a four-phase investigation workflow for technical issues and software defects.
