skills.rest
tony30552001
tony30552001COMMUNITY
Explore all skills by this author →
GitHub

investigate

Guide four-phase root-cause investigation of software failures with evidence gathering.

Updated Dec 26, 2025
Search Tags:#automation#troubleshoot#debug#investigate#root-cause#reproduction#stack-trace
One-click install
npx skills add https://github.com/tony30552001/Genpic-master --skill investigate-tony30552001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/tony30552001/Genpic-master/tree/main/.agents/skills/gstack/investigate
Command: npx skills add https://github.com/tony30552001/Genpic-master --skill investigate-tony30552001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams diagnose root causes quickly by guiding through four disciplined phases: investigate, analyze, hypothesize, implement. It enforces a strict rule: no fixes without identifying root cause.

Core Features & Use Cases

  • Guided four-phase debugging workflow (investigate, analyze, hypothesize, implement) that reduces guesswork.
  • Structured data collection from symptoms, traces, and repro steps to surface the root cause.
  • Use case: when a user reports intermittent errors or broken flows, run this skill to isolate the underlying bug and validate fixes.

Quick Start

Ask me to begin a root-cause investigation when you encounter a bug or error report.

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 or stack trace?▼

To find the root cause of a software bug, follow a guided four-phase debugging workflow that collects evidence from stack traces and repro steps before applying fixes. This enforces identifying the actual failure instead of guessing.

What is the best way to debug intermittent errors across services?▼

The best way to debug intermittent errors is using a guided root-cause investigation that structures data collection from symptoms and traces. This isolates the underlying bug by enforcing evidence gathering across codebases before implementing any fixes.

How do I start a root-cause investigation for unexpected behavior?▼

To start a root-cause investigation for unexpected behavior, initiate a structured debugging workflow that progresses through investigate, analyze, hypothesize, and implement phases. This ensures safe, traceable fixes by validating the underlying bug.

Can I use a structured debugging workflow to prevent guesswork in troubleshooting?▼

Yes, you can use a structured debugging workflow to prevent guesswork in troubleshooting by enforcing a strict rule: no fixes without identifying the root cause. It guides you through evidence gathering to safely validate fixes for software failures.

When should I use a guided root-cause analysis instead of direct fixes?▼

You should use a guided root-cause analysis instead of direct fixes when users report intermittent errors or broken flows. It ensures you isolate the underlying bug and validate fixes safely rather than applying patchwork changes.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

debug

Run structured debugging sessions to reproduce, isolate, and diagnose software errors.

Official
Intermediate
moberghrmoberghr
6

debugging-and-error-recovery

Reproduce failures, localize root causes, and verify fixes with builds and tests.

Official
Advanced
westnwestn
1

investigate

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

Community
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic