investigate

Guide hypothesis-driven bug investigations across local, staging, or production environments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to debugging by enforcing a root-cause-first mindset and documenting evidence before attempting fixes.

Core Features & Use Cases

  • Understand symptoms and reproduction details to scope the investigation.
  • Form 3 plausible hypotheses ranked by likelihood and gather evidence.
  • Design and run cheap, non-destructive tests to validate or rule out hypotheses.
  • Trace data flow and files to locate the root cause and document findings.
  • Escalate after 3 failed fix attempts and maintain a clear log for accountability.

Quick Start

Run the investigation workflow to begin formulating hypotheses and validating them with cheap tests.

Frequently Asked Questions about investigate

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

FAQPage Schema
What is hypothesis-driven debugging and when should I use it?

Hypothesis-driven debugging is a structured root-cause analysis approach that formulates plausible hypotheses, cheaply tests them, and traces data flow before applying fixes. Use it to systematically resolve complex bugs across local, staging, or production environments.

How do I find a root cause without blindly applying code fixes?

To find a root cause safely, you must understand symptoms, formulate three ranked hypotheses, run non-destructive tests to validate them, and trace data flow. Explicit root-cause determination is required before any fix attempts to ensure accountability.

What is the best way to structure a bug investigation workflow?

The best way to structure a bug investigation workflow is to enforce a step-by-step trace, rank hypotheses by likelihood, document evidence, and log outcomes. This maintains accountability and ensures rigorous root-cause analysis before fixes.

When should I escalate a bug investigation after repeated fix failures?

You should escalate a bug investigation after three failed fix attempts. The structured workflow enforces this limit and maintains a clear log of tested hypotheses and traced data flow to provide accountability for the escalation.

Can I use this structured debugging workflow across staging and production environments?

Yes, this structured debugging workflow supports investigations across local, staging, and production environments. It guides you through formulating hypotheses and running cheap, non-destructive tests to validate them safely in any environment.