Verified:GitHub

investigate

Investigate software failures through a four-phase evidence-first root-cause workflow.

Updated May 7, 2026

Search Tags:#debugging #root cause analysis #stack trace #incident response #error triage #evidence-based fixes #repository investigation

Ready to run

npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill investigate-tumeloramaphosa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/gstack/investigate
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill investigate-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you systematically debug broken software by identifying the true root cause before proposing any change. It prevents “fixing” symptoms that don’t address why the failure happened.

Core Features & Use Cases

Four-phase root-cause investigation: investigate, analyze, hypothesize, and implement a corrective path anchored to evidence.
Debug-trigger guidance: use it when you see errors, 500s, stack traces, or behavior that regressed since “it worked yesterday.”
Root-cause-first rule: follows the iron law of no fixes without identifying the underlying cause, reducing repeated outages and churn.

Quick Start

Invoke it by saying: investigate this error and identify the root cause, then propose and implement the smallest safe fix that is justified by evidence.

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 symptoms?▼

Root cause analysis identifies why software failures occur through a structured, evidence-first investigation workflow. It prevents surface fixes by requiring evidence confirmation before implementing any code changes.

What is the best way to debug a stack trace and identify why my application is broken?▼

Debugging a stack trace requires a structured root-cause investigation process that examines repository evidence. This approach drives through investigate, analyze, hypothesize, and implement phases to resolve unexpected runtime behavior.

How do I conduct incident response and error triage for a runtime regression?▼

Incident response and error triage for runtime regressions follow a four-phase investigation workflow. It enforces an iron law of no fixes without first confirming the underlying root cause using repository inspection tools.

Can I use this approach to fix errors without identifying the root cause first?▼

No, the root-cause-first rule explicitly prohibits implementing any fixes without confirming the root cause. This constraint reduces repeated outages and churn by ensuring every corrective path is justified by evidence.

What steps should I follow for evidence-based fixes during repository investigation?▼

Evidence-based fixes follow four sequential phases: investigate, analyze, hypothesize, and implement. You must use allowed tools for repository inspection to gather evidence and confirm the root cause before proposing the smallest safe fix.

When do I need root cause analysis instead of standard debugging for my application?▼

You need root cause analysis when you see errors, 500s, stack traces, or behavior that regressed since it worked yesterday. It applies to debugging requests like resolving why software is broken and preventing repeated outages.