systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: brmatola

Investigate and confirm root cause before applying fixes.

Updated Jan 17, 2026

Search Tags:#debugging #diagnostics #quality-assurance #reproduce #root-cause #hypothesis-testing

Ready to run

npx skills add https://github.com/brmatola/gremlins --skill systematic-debugging-brmatola

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

## 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

Phase-based workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation to structure debugging.
Reproducibility and evidence: guidance to reproduce issues, collect logs, and trace data flow across components.
Hypothesis-driven fixes: form a single hypothesis, test minimally, and verify results before proceeding.
Quick-start guidance for common scenarios: test failures, production bugs, and integration issues.

### Quick Start

Describe the failing behavior, reproduce it, gather evidence, then follow the four phases to identify and fix the root cause.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of a bug instead of just patching symptoms?▼

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.

What is the best way to debug flaky tests and production bugs systematically?▼

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.

How do I reproduce an integration failure to gather diagnostic evidence?▼

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.

Why should I use hypothesis testing when diagnosing software issues?▼

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.

Can I apply systematic debugging to performance problems and test failures?▼

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.

What should I do if my bug fix is not working as expected?▼

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.