skills.rest
amanik
amanikCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

investigate

Trace error symptoms to underlying causes using a structured four-phase debugging workflow.

Updated Mar 31, 2026
Search Tags:#debugging#investigate#root-cause#reproduction#phase-analysis#hypothesis-testing
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill investigate-amanik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/investigate
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill investigate-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root-cause investigation to prevent fixes that only address symptoms.

Core Features & Use Cases

  • Phased, structured approach guiding investigators through gather-evidence, analyze, hypothesize, and implement to locate and fix the actual root cause.
  • Clear escalation and decision points to avoid unsafe patches and ensure verifiable improvements.
  • Use case: when error traces are unclear, or a regression requires understanding the underlying mechanism before changes.

Quick Start

Describe observed symptoms and reproduce steps, then proceed to Phase 1 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 software bug instead of just fixing the symptom?▼

Root-cause debugging uses a structured four-phase workflow—gather evidence, analyze, hypothesize, and implement—to trace error traces and performance regressions to their underlying mechanism before applying fixes.

What is the best way to debug a performance regression when the error trace is unclear?▼

Debugging an unclear regression requires describing observed symptoms and reproduction steps, then using phase analysis to collect evidence and test hypotheses before changing code.

How do I systematically investigate a crash across my codebase?▼

Investigating a crash involves a phased workflow that collects evidence, analyzes the trace, tests hypotheses against the codebase, and escalates unsafe patches to ensure verifiable improvements.

When should I use a structured debugging workflow for an error trace?▼

A structured debugging workflow is needed when error traces are unclear, crashes require understanding the underlying mechanism, or regressions demand hypothesis testing before safe fixes.

Can I use root-cause debugging to prevent unsafe patches to my codebase?▼

Yes, root-cause debugging includes clear escalation and decision points during the hypothesis and implementation phases to avoid unsafe patches and ensure verifiable improvements.

What steps should I follow to reproduce and analyze a software bug before fixing it?▼

Start by describing observed symptoms and reproduction steps, then proceed through evidence gathering, phase analysis, and hypothesis testing to locate the actual root cause before implementing changes.

Related Skills

Explore More Software Engineering Skills→
amrhas82amrhas82
21

systematic-debugging

Identify root causes in software bugs using a four-phase investigation framework.

Community
Basic
pcaokhaipcaokhai

investigate

Trace software bugs to root causes through a structured multi-phase investigation workflow.

Community
Advanced
wpankwpank
11

logging-observability

Implement structured logging, OpenTelemetry tracing, and RED/USE metrics.

Community
Advanced
kk20300113-pngkk20300113-png

investigate

Guide structured root-cause debugging for software errors and regressions.

Community
Advanced