skills.rest
alexaundre
alexaundreCOMMUNITY
Explore all skills by this author →
GitHub

investigate

Identify root causes of software errors through a four-phase debugging workflow.

Updated Aug 27, 2026
Search Tags:#debugging#reproducibility#root-cause#log-analysis#incident-response#hypothesis-testing
One-click install
npx skills add https://github.com/alexaundre/mycc --skill investigate-alexaundre
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/alexaundre/mycc/tree/main/.claude/skills/investigate
Command: npx skills add https://github.com/alexaundre/mycc --skill investigate-alexaundre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined, evidence-driven debugging workflow so engineers do not patch symptoms without identifying the true root cause. It helps teams reduce regressions and wasted effort by guiding a consistent investigation from logs and stack traces to validated fixes.

Core Features & Use Cases

  • Four-phase framework: root-cause investigation, pattern analysis, hypothesis validation, and implementation verification.
  • Reproducible validation: design and execute tests, logging, or minimal repro cases to prove or falsify hypotheses.
  • Actionable outputs: concise symptom summary, root cause with evidence, step-by-step verification, recommended fix, and regression test guidance.
  • Use Case: Diagnose intermittent crashes by extracting stack traces, locating the triggering code region, forming hypotheses about state or race conditions, and producing a tested patch with regression checks.

Quick Start

Invoke /investigate with the error message, stack trace, and the relevant code context to start a structured 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 perform root-cause analysis for intermittent software crashes using stack traces?▼

A structured debugging workflow investigates root causes through four phases: root-cause investigation, pattern analysis, hypothesis validation, and implementation verification, ensuring fixes address true causes not symptoms.

How do I systematically debug unexpected system failures from log analysis?▼

Systematic debugging of unexpected failures applies a four-phase framework—root-cause investigation, pattern analysis, hypothesis validation, and implementation verification—to transform logs and stack traces into actionable fixes and regression tests.

How do I validate debugging hypotheses with reproducible test cases?▼

Validate debugging hypotheses by designing and executing tests, adding logging, or building minimal reproduction cases to prove or falsify suspected root causes before applying code fixes.

What's the best way to find the root cause of an error before applying a code fix?▼

Finding the true root cause before patching requires evidence-driven investigation that outputs a symptom summary, root cause with evidence, step-by-step verification, recommended fix, and regression test guidance.

Can I use hypothesis-driven validation for ops incident response scenarios?▼

Hypothesis-driven validation applies to ops incident response scenarios where logs, stack traces, and code context are available, systematically verifying suspected triggers before deploying patches.

Related Skills

Explore More Software Engineering Skills→
icartshicartsh
4

error-detective

Parse stack traces and guide error resolution with the TRACE framework.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
mymx2mymx2
4

stacktrace-log-triage

Diagnose Kotlin and Spring failures by analyzing stack traces and startup logs.

Community
Advanced
yun520-1yun520-1
38

code-analyzer

Analyze codebases for architectural patterns, code quality, and DDD elements.

Community
Advanced