investigate

Guide a debugging workflow to identify root causes of software defects.

4|1|Updated Sep 13, 2023

Search Tags:#debugging #investigate #phases #hypothesis #root-cause #root-cause-analysis

Ready to run

npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill investigate-louisfghbvc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/investigate
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill investigate-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root-cause investigation helps engineers move beyond symptom-fixing by enforcing a repeatable workflow across four phases: investigate, analyze, hypothesize, implement, so fixes address the real problem and prevent regressions.

Core Features & Use Cases

Four-phase debugging workflow guides you from symptom collection to root-cause confirmation.
Structured evidence gathering, hypothesis testing, and cautious change planning reduce guesswork and risk.
Use cases include flaky APIs, production incidents, and hard-to-reproduce bugs where guided analysis accelerates resolution.

Quick Start

Describe the bug and paste the error details; I will initiate the root-cause investigation workflow.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I find the root cause of a bug using a structured debugging workflow?▼

Root-cause debugging systematically identifies software defects through a four-phase workflow: collecting symptoms, correlating evidence, testing hypotheses, and planning safe fixes to address the real problem and prevent regressions.

What's the best way to debug flaky APIs and hard-to-reproduce production incidents?▼

Debugging flaky APIs and production incidents requires structured evidence gathering and hypothesis testing, accelerating resolution by moving beyond symptom-fixing to confirm the actual root cause through guided analysis.

What information do I need to start a root-cause analysis for a software defect?▼

Root-cause analysis requires clear symptoms, reproduction steps, logs or traces, and access to relevant code context to drive structured hypothesis testing and safe fixes for the encountered software defect.

When should I use a systematic hypothesis testing approach instead of patching symptoms?▼

Systematic hypothesis testing is needed for software defects, stack traces, exceptions, and inconsistent behavior where deterministic reproduction is possible, ensuring fixes address the real problem and prevent regressions.

Can I investigate inconsistent behavior and stack traces in staging environments?▼

Yes, this debugging workflow focuses on software defects encountered in development, staging, or production, analyzing stack traces, exceptions, and inconsistent behavior through structured evidence correlation.

Why does root-cause investigation use four phases for software debugging?▼

Root-cause investigation uses four phases—investigate, analyze, hypothesize, implement—to enforce a repeatable workflow that reduces guesswork and risk while ensuring fixes address the real problem and prevent regressions.