investigate

Guide structured four-phase root-cause debugging for software issues.

3|3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tsensei/ReelMistri --skill investigate-tsensei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/tsensei/ReelMistri/tree/main/.claude/skills/gstack/investigate
Command: npx skills add https://github.com/tsensei/ReelMistri --skill investigate-tsensei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging framework that guides you from symptoms to root cause, reducing blind fixes and wasted time.

Core Features & Use Cases

  • Four-phase workflow: investigate, analyze, hypothesize, implement.
  • AskUserQuestion prompts for missing context to keep debugging deterministic.
  • WebSearch, Grep, Read, Write and Bash tooling to explore code, logs, and external sources.
  • Real-world scenarios include debugging flaky APIs, memory leaks, or CI failures.

Quick Start

Describe the failing behavior you want to debug, and this skill will guide you through a four-phase root-cause investigation.

Frequently Asked Questions about investigate

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

FAQPage Schema
What is the best way to find the root cause of a software bug or runtime failure?

Root-cause debugging uses a structured four-phase workflow—investigate, analyze, hypothesize, implement—to guide you from symptoms to a verified fix, reducing blind patches and wasted time.

How do I debug flaky APIs, memory leaks, or CI failures systematically?

Systematic debugging applies a four-phase workflow to flaky APIs, memory leaks, or CI failures, using tools like Grep, Read, and Bash to explore code, logs, and configurations.

Can I use web searches to ground findings during a root-cause investigation?

Yes, the debugging workflow optionally performs web searches to ground findings, while also prompting for missing context via questions to keep the investigation deterministic.

How do I start debugging when I only have a vague description of the failing behavior?

Describe the failing behavior to start the investigation, and the workflow will prompt you with targeted questions for missing context to ensure deterministic analysis.

Does structured debugging work for errors across both code and runtime environments?

Structured debugging applies to errors, bugs, or failures across code, configurations, and runtime environments, systematically guiding you from symptoms to a verified fix.