investigate

Name: investigate
Availability: InStock
Author: singhianand23045

Identify root causes of bugs through systematic four-phase investigation.

Updated Apr 12, 2026

Search Tags:#debugging #bash #grep #investigate #root-cause #websearch #stack-trace

Ready to run

npx skills add https://github.com/singhianand23045/GarryTan --skill investigate-singhianand23045

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/singhianand23045/GarryTan/tree/main/investigate
Command: npx skills add https://github.com/singhianand23045/GarryTan --skill investigate-singhianand23045

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis".

Core Features & Use Cases

Structured root-cause analysis: collect symptoms, read code, and check recent changes.
Interactive prompts: AskUserQuestion to gather missing information and steer the investigation.
Context-aware tooling: uses Bash, Read, Write, Edit, Grep, Glob, WebSearch to gather evidence, reproduce issues, and verify hypotheses.

Quick Start

Describe the failing behavior and run the investigate workflow to begin root-cause analysis.

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 stack trace?▼

To find the root cause of a bug from a stack trace, you collect symptoms, trace code paths, and examine recent changes. This skill applies a four-phase approach: investigate, analyze, hypothesize, and implement.

What is the best way to systematically debug unexpected behavior in my codebase?▼

Systematic debugging of unexpected behavior requires gathering evidence, interacting with the user, and reproducing scenarios. The workflow enforces an Iron Law: no fixes without root cause, ensuring you resolve the actual fault.

Can I use grep and bash to investigate errors across multiple files?▼

Yes, you can use bash and grep to investigate errors across files. The workflow uses context-aware tooling including Bash, Grep, Glob, and Read to gather evidence, read code, and check recent changes.

Does this debugging workflow support web search for unknown error messages?▼

Yes, the debugging workflow supports web search for unknown error messages. It uses WebSearch alongside interactive prompts to gather missing information and steer the root-cause investigation when encountering unfamiliar issues.

When should I use a root-cause analysis workflow instead of directly patching code?▼

You should use a root-cause analysis workflow instead of directly patching code when asked to debug, fix, or investigate why something is broken. It prevents superficial fixes by tracing code paths before implementing changes.

How do I reproduce a failing scenario during root cause analysis?▼

To reproduce a failing scenario during root cause analysis, you use Bash and interactive prompts to gather evidence and verify hypotheses. The workflow collects symptoms and traces code paths before applying fixes.