investigate

Name: investigate
Availability: InStock
Author: fxhollow

Guide root-cause debugging through investigate, analyze, hypothesize, and implement phases.

Updated Mar 26, 2026

Search Tags:#debugging #investigation #code-analysis #hypothesis #root-cause #reproduction

Ready to run

npx skills add https://github.com/FxHollow/100000mrr-landing --skill investigate-fxhollow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/FxHollow/100000mrr-landing/tree/main/.agents/skills/gstack/investigate
Command: npx skills add https://github.com/FxHollow/100000mrr-landing --skill investigate-fxhollow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root cause investigation to avoid patching symptoms. It enforces a disciplined four-phase approach: investigate, analyze, hypothesize, implement. The Iron Law: no fixes without root cause.

Core Features & Use Cases

Structured four-phase debugging workflow guiding users from symptoms to root cause.
Tools integration: Bash, Read, Write, Edit, Grep, Glob, AskUserQuestion, WebSearch for evidence gathering and interaction.
Scope control and governance: scope lock, proactive flagging, telemetry, and audit-ready documentation when debugging complex bugs.

Quick Start

Describe the bug and reproduce steps, then I will begin root-cause investigation.

Frequently Asked Questions about investigate

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

FAQPage Schema

What is root-cause debugging and how does it prevent symptom patching?▼

Root-cause debugging is a systematic workflow that enforces evidence gathering and hypothesis testing before applying fixes. It prevents symptom patching by requiring a documented root cause through a structured investigate, analyze, hypothesize, and implement process.

How do I investigate a software bug using a structured debugging workflow?▼

To investigate a software bug, describe the bug and reproduction steps. The workflow then guides you through gathering symptoms, reading code, checking changes, and reproducing scenarios to form a stepwise root-cause hypothesis before any implementation.

Can I use this debugging workflow for complex bugs across large codebases?▼

Yes, you can use this workflow for complex bugs across codebases. It includes scope lock, proactive flagging, telemetry, and audit-ready documentation to maintain governance and safety while investigating errors.

What is the best way to document root-cause hypotheses during code analysis?▼

The best way to document root-cause hypotheses is through the formal investigation workflow, which mandates structured evidence collection and audit-ready documentation alongside stepwise hypothesis testing to validate the root cause.

When should I lock scope during a root-cause investigation?▼

You should lock scope during root-cause investigation when debugging complex bugs to prevent uncontrolled changes. Scope lock is a safety check that ensures fixes target only the validated root cause without introducing regressions.