investigate

Guide structured four-phase debugging to isolate root causes in software systems.

1|Updated Feb 25, 2026

Search Tags:#debug #grep #root-cause #websearch #incident-analysis #askuserquestion

Ready to run

npx skills add https://github.com/alexandervashurin/semaphore --skill investigate-alexandervashurin

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root cause investigation through four phases: investigate, analyze, hypothesize, and implement. The Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", or "root cause analysis". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working.

Core Features & Use Cases

Structured four-phase workflow for debugging and root-cause analysis.
Proactive prompts and guidance to identify symptoms, gather evidence, and test hypotheses.
Integrated tools (AskUserQuestion, WebSearch, Grep) to collect information and propose fixes.

Quick Start

Provide a reproducible debugging scenario and initiate the four-phase plan to identify the root cause.

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 in my codebase?▼

A root cause analysis for software systems requires gathering evidence and testing hypotheses systematically. This skill guides a four-phase workflow—investigate, analyze, hypothesize, implement—using tools like grep and web search to isolate the underlying issue before any fixes are applied.

What is the best way to debug flaky behavior across services?▼

The best way to debug flaky behavior across services is following a structured investigation workflow that enforces the rule of no fixes without root cause. It proactively prompts you to identify symptoms, gather evidence, and test hypotheses across your codebase to isolate the problem.

How do I start a root cause analysis when troubleshooting an incident?▼

To start root cause analysis during incident troubleshooting, provide a reproducible debugging scenario to initiate the structured four-phase plan. The workflow uses prompt-driven tools to collect information, identify symptoms, and guide you toward proposing fixes.

Can I use this approach to fix performance regressions without finding the root cause?▼

No, you cannot use this approach to fix performance regressions without finding the root cause. The workflow enforces an iron law of no fixes without root cause, ensuring you must isolate the underlying issue through evidence gathering and hypothesis testing before implementing any changes.

How does a structured debugging workflow isolate issues in software systems?▼

A structured debugging workflow isolates issues in software systems by guiding you through four phases: investigate, analyze, hypothesize, and implement. It integrates tools like grep, web search, and user questions to collect evidence and test hypotheses against the observed symptoms.