skills.rest
effiraid
effiraidCOMMUNITY
Explore all skills by this author →
GitHub

investigate

Guides engineers through a four-phase workflow for systematic bug root-cause analysis.

Updated Aug 23, 2026
Search Tags:#automation#debugging#investigation#root-cause#reproduction#tests
One-click install
npx skills add https://github.com/effiraid/reflix-nextjs --skill investigate-effiraid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/effiraid/reflix-nextjs/tree/main/.claude/skills/gstack/investigate
Command: npx skills add https://github.com/effiraid/reflix-nextjs --skill investigate-effiraid

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". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working.

Core Features & Use Cases

  • Four-phase workflow: investigate, analyze, hypothesize, implement.
  • Proactively propose hypotheses and evidence-based steps to reproduce and verify fixes.
  • Supports guided responses via Bash, Read, Write, Edit, Grep, Glob, AskUserQuestion, and WebSearch.

Quick Start

Describe the observed issue and reproduce steps to start 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 perform root-cause analysis for a software bug?▼

Structured root-cause analysis uses a four-phase workflow: investigate, analyze, hypothesize, and implement. It enforces evidence-based hypotheses and reproducible steps to identify bug origins before implementing fixes.

What is the best way to debug a code regression systematically?▼

Systematically debugging a code regression involves reproducing the error, forming evidence-based hypotheses, and writing regression tests before fixing the code. A structured approach prevents patching symptoms without addressing the underlying root cause.

Why should I find a root cause before fixing a broken feature?▼

Fixing a broken feature without finding the root cause often leads to recurring issues. An evidence-based debugging workflow enforces the rule of no fixes without root cause, ensuring the actual origin is addressed and verified with regression tests.

Can I use a structured debugging workflow for performance issues?▼

Yes, a structured debugging workflow applies to performance issues alongside errors and regressions. It guides engineers through investigating runtime environments and codebases to form evidence-based hypotheses and verify performance fixes with regression tests.

How do I start troubleshooting an unexpected error in my codebase?▼

To start troubleshooting an unexpected error, describe the observed issue and provide the steps to reproduce it. This initiates a root-cause investigation workflow that analyzes the codebase and runtime environment to form evidence-based hypotheses.

Related Skills

Explore More Software Engineering Skills→
All-The-VibesAll-The-Vibes
50

reproduce-bug

Reproduce bugs from GitHub issues and document findings.

Official
Advanced
ComputerConnectionComputerConnection

investigate

Guides root-cause investigation through a four-phase debugging workflow.

Community
Advanced
ClipboardHealthClipboardHealth
66

flaky-test-debugger

Diagnose intermittent test failures and recommend fixes from logs and code.

Official
Advanced
Chang-Shih-YungChang-Shih-Yung

gstack-openclaw-investigate

Enforces a four-phase root cause workflow for web and backend system debugging.

Community
Advanced