skills.rest
martin-hsu-test
martin-hsu-testCOMMUNITY
Explore all skills by this author →
GitHub

investigate

Identify root causes of software failures through structured four-phase debugging.

1|Updated Apr 8, 2026
Search Tags:#debugging#investigation#reproduce#hypothesis#root-cause#bug#stack-trace
One-click install
npx skills add https://github.com/martin-hsu-test/gstack-gemini-slim --skill investigate-martin-hsu-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/martin-hsu-test/gstack-gemini-slim/tree/main/.gemini/skills/gstack-investigate
Command: npx skills add https://github.com/martin-hsu-test/gstack-gemini-slim --skill investigate-martin-hsu-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root-cause investigation to stop chasing symptoms and fix the actual cause.

Core Features & Use Cases

  • Four phases: investigate, analyze, hypothesize, implement.
  • Proactive guidance to structure bug reproduction and validation.
  • Works across codebases to reduce MTTR and prevent regression.

Quick Start

Ask for a bug report with errors, stack traces, and reproduction steps to begin root-cause investigation.

Frequently Asked Questions about investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to find the root cause of a software bug from a stack trace?▼

Root-cause debugging follows a four-phase process: investigate, analyze, hypothesize, and implement. It structures bug reproduction and validation by collecting evidence and testing hypotheses before applying fixes, ensuring safe remediation.

How do I systematically reproduce an intermittent bug across my codebase?▼

To systematically reproduce an intermittent bug, use a structured debugging workflow that proactively guides bug reproduction and validation. It analyzes reported symptoms and stack traces to form and test hypotheses across codebases.

Can I use a structured debugging workflow for any reported software error?▼

Yes, structured debugging applies whenever users report errors, stack traces, or intermittent bugs across codebases. It reduces mean time to recovery and prevents regression through disciplined evidence collection and hypothesis testing.

What do I need to start a root-cause investigation for a failing application?▼

To start a root-cause investigation, provide a bug report containing errors, stack traces, and reproduction steps. This input initiates the four-phase process to identify the actual cause of the software failure.

Why does fixing a symptom not stop my bug from recurring?▼

Fixing a symptom fails to stop recurrence because the underlying issue remains. A systematic root-cause debugging workflow identifies the actual cause through evidence collection and hypothesis testing to implement lasting fixes.

Does systematic debugging help prevent regression after implementing a fix?▼

Yes, systematic debugging prevents regression by logging learnings during the fix implementation phase. This disciplined process ensures safe, repeatable remediation across codebases and reduces future mean time to recovery.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
anionzoanionzo

debug

Diagnose build, test, and runtime failures to identify root causes.

Community
Advanced
mwaymway
4

systematic-debugging

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

Community
Advanced
huyhung9630huyhung9630
1

omc-ultraqa

Run tests, diagnose failures, and apply fixes until quality conditions are met.

Community
Advanced