investigate

Diagnose code issues through a four-phase root-cause investigation workflow.

Updated Mar 29, 2026

Search Tags:#workflow #debugging #reproduce #code-analysis #root-cause #regression-test

Ready to run

npx skills add https://github.com/zzxtbeta/design-handbook --skill investigate-zzxtbeta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/zzxtbeta/design-handbook/tree/main/.agents/skills/gstack/investigate
Command: npx skills add https://github.com/zzxtbeta/design-handbook --skill investigate-zzxtbeta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging framework that ensures root-cause analysis before applying any fix.

Core Features & Use Cases

Four-phase root-cause workflow (investigate, analyze, hypothesize, implement).
Scoped debugging with optional freeze/scope-lock to limit changes during a debugging session.
Guidance for reproducibility, evidence gathering, and escalation when needed.

Quick Start

Run the root-cause investigation by collecting symptoms, tracing code paths, and forming a testable hypothesis before making any changes.

Frequently Asked Questions about investigate

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

FAQPage Schema

What is a systematic root-cause debugging workflow?▼

A systematic root-cause debugging workflow enforces issue diagnosis before applying fixes by collecting symptoms, tracing code paths, and forming testable hypotheses to ensure deterministic reproduction.

How do I debug code by forming a root-cause hypothesis?▼

To debug code by forming a root-cause hypothesis, collect symptoms, read the code path, and establish a testable hypothesis. You then validate evidence before attempting any scope-locked fixes.

How do I reproduce a bug deterministically during code analysis?▼

To reproduce a bug deterministically during code analysis, gather evidence and trace the execution path to validate your root-cause hypothesis before isolating the fix and proposing regression tests.

When should I lock scope during a debugging session?▼

You should lock scope during a debugging session to limit unrelated changes when investigating complex issues. This optional freeze isolates the root cause by focusing strictly on the current code analysis path.

Why should I write regression tests after fixing a bug?▼

Writing regression tests after fixing a bug ensures the root-cause hypothesis is permanently resolved. The debugging workflow validates evidence and proposes fixes alongside these tests to prevent future recurrence.