skills.rest
hetsheth-droid
hetsheth-droidCOMMUNITY
Explore all skills by this author →
GitHub

investigate

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

Updated Mar 31, 2026
Search Tags:#workflow#debugging#evidence#investigate#phases#root-cause
One-click install
npx skills add https://github.com/hetsheth-droid/toolbox-template --skill investigate-hetsheth-droid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/hetsheth-droid/toolbox-template/tree/main/incubating/gstack/investigate
Command: npx skills add https://github.com/hetsheth-droid/toolbox-template --skill investigate-hetsheth-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging protocols to identify root causes before applying fixes, reducing wasted effort chasing symptoms.

Core Features & Use Cases

  • Four-phase approach: investigate, analyze, hypothesize, implement.
  • Proactive invocation when errors or issues are reported, with structured evidence collection.
  • Comprehensive runbook for reproducibility, hypotheses, and verification.

Quick Start

Describe the issue and ask Claude to start a root-cause investigation with the provided symptoms.

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 when do I need a structured investigation workflow?▼

Root-cause debugging identifies the underlying source of errors or unexpected behavior rather than just treating symptoms. You need a structured investigation workflow when repeatedly fixing surface issues fails to resolve persistent bugs across your codebase.

How do I debug a crash using a four-phase investigation approach?▼

Debug a crash by progressing through four phases: investigate to collect evidence, analyze the findings, hypothesize the root-cause, and implement the verified fix. This ensures you document reproducibility and resolve the actual error source.

What's the best way to stop chasing symptoms and find the real fix for a bug?▼

The best way to find the real fix is applying a systematic debugging protocol that enforces evidence collection and hypothesis documentation. By verifying fixes before deployment, you stop wasting effort chasing symptoms and resolve the actual root-cause.

Does root-cause debugging work for any type of error or unexpected behavior in my codebase?▼

Yes, this structured root-cause debugging applies to bugs, errors, crashes, and unexpected behavior across codebases. The investigation workflow proactively handles diverse reported issues by standardizing evidence collection and verification phases.

How do I document debugging evidence for reproducibility before deploying a fix?▼

Document debugging evidence by maintaining a comprehensive runbook during the investigation and analysis phases. Record symptoms, collected evidence, hypotheses, and verification steps to ensure reproducibility before deploying implemented fixes.

Why does my bug fix keep failing after deployment when the issue seemed resolved?▼

Bug fixes fail after deployment when the root-cause was not properly identified, meaning only symptoms were patched. A structured investigation workflow prevents this by enforcing evidence collection and hypothesis verification before implementation.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
jnlanahanjnlanahan

runbook

Generate RUNBOOK.md with environment variables, health checks, failure fixes, and rollback steps.

Community
Advanced
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
htlin222htlin222
77

error-detective

Search and analyze log files and codebases for error patterns and stack traces.

Community
Intermediate