investigate

Name: investigate
Availability: InStock
Author: lapagayo

Guide users through a four-phase debugging workflow to diagnose root causes.

1|Updated Mar 31, 2026

Search Tags:#workflow #debugging #investigate #analyze #root-cause #implement #hypothesize

Ready to run

npx skills add https://github.com/LaPaGaYo/nexus --skill investigate-lapagayo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/support/investigate
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill investigate-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or is troubleshooting why something stopped working. (Nexus)

Core Features & Use Cases

Four-phase structured debugging: investigate, analyze, hypothesize, implement.
Proactive safety: checks debug scope boundary and avoids breaking context.
Guided runtime for persistent sessions and staged recovery.

Quick Start

Run the investigate workflow on the reported issue to preserve context and triage root causes.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I systematically debug a software bug to find the root cause?▼

To debug systematically, follow a four-phase workflow: investigate the runtime anomaly, analyze the stack trace, hypothesize the root cause, and implement the fix. This enforces the iron law of no fixes without root cause.

What is the best way to troubleshoot runtime anomalies and errors?▼

Troubleshoot runtime anomalies using a four-phase workflow: investigate, analyze, hypothesize, and implement. This staged approach proactively checks debug scope boundaries to avoid breaking context during the session.

How do I analyze a stack trace without breaking the debugging context?▼

To analyze a stack trace without breaking context, use a guided runtime that preserves session state. The debugging workflow proactively checks debug scope boundaries and uses staged recovery to maintain context integrity.

What tools do I need to investigate errors and test debugging hypotheses?▼

Investigating errors and testing hypotheses requires integration with Bash, Read, Write, Edit, Grep, Glob, AskUserQuestion, and WebSearch. These tools gather data, test hypotheses, and load routing guidance during the workflow.

When should I use a structured debugging workflow for troubleshooting?▼

Use a structured debugging workflow when asked to "debug this", "fix this bug", or "investigate this error". It is essential for troubleshooting why something stopped working and ensuring no fixes are applied without root cause confirmation.