debug-detective

Automate root-cause debugging investigations for software bugs.

3|2|Updated Jun 9, 2026

Search Tags:#workflow #debugging #hypothesis #root-cause #bisect #reproduction

Ready to run

npx skills add https://github.com/JayRHa/AgentSkills --skill debug-detective-jayrha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-detective
Source: https://github.com/JayRHa/AgentSkills/tree/main/debug-detective
Command: npx skills add https://github.com/JayRHa/AgentSkills --skill debug-detective-jayrha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Debugging often relies on guesswork and incomplete observations. This Skill provides a disciplined, evidence-first process to systematically reproduce, isolate, hypothesize, and verify root causes of software defects.

Core Features & Use Cases

Structured workflow: follows capture → reproduce → isolate → hypothesize → experiment → diagnose → fix → verify to locate root causes.
Templates & references: includes investigation templates and reference materials to guide every step, from logs to hypothesis logs.
Adaptable to multiple contexts: applicable to crashes, flaky tests, and environment discrepancies across local, CI, and production.

Quick Start

Describe a failing scenario and trigger the reproducible debug investigation.

Frequently Asked Questions about debug-detective

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

FAQPage Schema

How do I systematically find the root cause of a flaky test?▼

To root-cause flaky tests, follow a structured debugging workflow: capture the failure, reproduce it, isolate variables, hypothesize, experiment, diagnose, fix, and verify using provided investigation templates.

What is the best way to debug an intermittent crash across different environments?▼

Debugging intermittent crashes across local, CI, and production environments requires an evidence-first process to systematically reproduce, isolate, hypothesize, and verify the root cause using structured investigation templates.

How do I reproduce a software bug when I only have an incomplete bug report?▼

Reproducing a bug from an incomplete report starts with capturing available evidence, then systematically isolating variables and testing hypotheses to verify the root cause through a disciplined workflow.

Can I use a hypothesis-driven workflow for debugging production crashes?▼

Yes, a hypothesis-driven debugging workflow applies to production crashes, flaky tests, and environment discrepancies, providing a repeatable process to capture, isolate, experiment, and verify root causes with evidence.

What steps are involved in an evidence-first debugging investigation?▼

An evidence-first debugging investigation follows the steps of capture, reproduce, isolate, hypothesize, experiment, diagnose, fix, and verify to systematically locate and resolve software defect root causes.

Why does guessing during root-cause analysis fail for complex software defects?▼

Root-cause analysis fails when relying on guesswork and incomplete observations, whereas a disciplined, evidence-first workflow systematically reproduces, isolates, and verifies hypotheses to accurately locate software defects.