investigate

Collect symptoms and trace code paths to locate root causes.

2|Updated Mar 31, 2026

Search Tags:#debugging #grep #investigate #root-cause #stack-trace #git-log

Ready to run

npx skills add https://github.com/jayzalowitz/skytwin --skill investigate-jayzalowitz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/jayzalowitz/skytwin/tree/main/.claude/skills/gstack/investigate
Command: npx skills add https://github.com/jayzalowitz/skytwin --skill investigate-jayzalowitz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root-cause investigation to avoid silent fix-attempts and repeated outages.

Core Features & Use Cases

Structured problem gathering: collects symptoms, traces errors, and documents steps to reproduce.
Root-cause analysis: traces code paths, checks recent changes, and proposes verifiable hypotheses.
Guided remediation: tests hypotheses, locks scope, and documents the final root cause with evidence.

Quick Start

Train the system to start a root-cause investigation whenever you report a bug, then follow the eight-step flow to identify the root cause and implement a verified fix.

Frequently Asked Questions about investigate

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

FAQPage Schema

What is root-cause debugging and when do I need it for software bugs?▼

Root-cause debugging systematically collects symptoms, traces code paths, and documents findings to fix software bugs, timeouts, and regressions. You need it when silent fix-attempts fail or repeated outages occur across modules.

How do I investigate a stack trace to find a root cause?▼

To investigate a stack trace, collect symptoms, read the code path to locate root causes, and document findings. The process involves checking recent git history, grepping code, and running non-destructive checks to propose verifiable hypotheses.

How to debug a regression issue across multiple modules step by step?▼

Debugging a regression across modules requires an eight-step flow: gather symptoms, trace errors, read code paths, check git history, grep code, run non-destructive checks, test hypotheses, and document the verified root cause with evidence.

Can I use git log and grep to trace recent code changes during a debugging investigation?▼

Yes, you can use git log and grep to trace recent code changes during a debugging investigation. The skill supports reading git history and grepping code to identify regressions and propose verifiable hypotheses for remediation.

What's the best way to document root-cause analysis findings for a verified fix?▼

The best way to document root-cause analysis is to record symptoms, reproducible steps, tested hypotheses, and the final root cause with evidence. This guided remediation approach locks scope and prevents silent fix-attempts or repeated outages.

Why do my bug fixes keep failing without a systematic root-cause investigation?▼

Bug fixes fail without systematic root-cause investigation because silent fix-attempts skip symptom collection and code path tracing. A structured eight-step flow identifies the actual root cause, tests hypotheses, and documents evidence before shipping a verified fix.