investigate

Guide engineers through a phased root-cause debugging workflow with evidence gates.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/zeveck/zskills --skill investigate-zeveck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/zeveck/zskills/tree/main/skills/investigate
Command: npx skills add https://github.com/zeveck/zskills --skill investigate-zeveck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep debugging for complex bugs. Enforces a disciplined workflow: reproduce, trace, state root cause, fix, verify. The agent must PROVE it understands the root cause before writing any fix.

Core Features & Use Cases

  • Phase-guided investigation: reproduce, trace, define root cause, fix, and verify.
  • Evidence-driven root-cause statements and gates for safe, reliable fixes.
  • Supports single-bug investigations and escalation when batch fixes are inappropriate.

Quick Start

Initiate an investigation with /investigate <description> to reproduce the bug, trace the root cause, and validate a fix.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I prove root cause before coding a bug fix?

Proving root cause requires a disciplined debugging workflow that enforces reproduction, tracing, and evidence collection before writing any fix, ensuring you fully understand the issue.

What is the best way to structure root-cause debugging for complex bugs?

The best way to structure root-cause debugging is through a phase-guided workflow that moves sequentially through reproduction, tracing, defining the root cause, fixing, and structured verification.

How do I perform regression planning during a bug investigation?

Regression planning during a bug investigation is integrated into the verification phase, requiring you to define the root cause and collect evidence to validate a fix before finalizing code changes.

When should I use a structured investigation instead of batch fixing bugs?

You should use a structured investigation instead of batch fixing when dealing with complex single-bug cases that require strict phase gates, reproduction, and proof of root cause before applying any fixes.

How do I verify a bug reproduction before attempting a fix?

To verify a bug reproduction before a fix, the investigation workflow requires you to trace the issue and state the root cause with evidence, acting as a gate to ensure safe, reliable code changes.