Verified:Website 𝕏@ishandutta2007 GitHub

Systematic Diagnosis

Diagnose hard bugs and performance regressions via deterministic reproduction before fixes.

13|8|Updated May 8, 2026

Search Tags:#debugging #root cause analysis #hypothesis testing #instrumentation #regression tests #performance regression #deterministic reproduction

Ready to run

npx skills add https://github.com/ishandutta2007/Awesome-Claude-Skills --skill systematic-diagnosis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Systematic Diagnosis
Source: https://github.com/ishandutta2007/Awesome-Claude-Skills/tree/main/skills
Command: npx skills add https://github.com/ishandutta2007/Awesome-Claude-Skills --skill systematic-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose complex failures and performance regressions with evidence-based steps instead of guesses.

Core Features & Use Cases

Feedback-loop-first diagnosis: Builds a deterministic test or harness to reproduce the symptom before hypothesizing.
Falsifiable hypotheses: Produces ranked, testable explanations with clear predictions.
Targeted instrumentation: Adds minimal, tagged probes to validate assumptions.
Verified regression: Writes a regression test at the correct seam, then confirms the fix passes and instability is removed.

Quick Start

Ask for the Systematic Diagnosis skill and provide your failure description plus any logs, stack trace, and how the problem currently manifests so it can create a deterministic reproduction case.

Frequently Asked Questions about Systematic Diagnosis

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

FAQPage Schema

How do I debug an intermittent failure that only happens in specific environments?▼

Debug intermittent failures by building a deterministic reproduction harness that reliably triggers the symptom before proposing root cause analysis or fixes. This establishes a fast feedback loop to verify the exact environment-specific conditions causing the failure.

What is the best way to find the root cause of a performance regression?▼

Find the root cause of a performance regression by applying falsifiable hypothesis testing with one-variable instrumentation. You add minimal tagged probes to validate assumptions, generating ranked explanations with clear predictions to isolate the exact bottleneck.

How do I start diagnosing a complex bug when I only have a stack trace and logs?▼

Start diagnosing a complex bug by providing your failure description along with the stack trace and logs to create a deterministic reproduction case. This reproduction-first constraint ensures you verify the symptom consistently before generating any testable explanations or fixes.

Does hypothesis testing work for fixing hard bugs without guessing?▼

Hypothesis testing works for hard bugs by producing ranked, falsifiable explanations with clear predictions instead of guesses. You validate these assumptions through targeted instrumentation, adding minimal tagged probes to confirm or rule out specific failure mechanisms.

How do I write a regression test to verify my bug fix is correct?▼

Write a regression test at the correct seam to verify your bug fix, then confirm the test passes and the instability is removed. This verified regression proves the fix resolves the exact issue while preventing future reintroduction of the failure.

When should I avoid systematic diagnosis for debugging?▼

Avoid systematic diagnosis when you cannot establish a deterministic reproduction of the failure, because the methodology strictly requires a reproducible test case before proposing explanations. Intermittent issues lacking measurable verification are unsuitable until a consistent harness is built.