investigate

Collect symptoms, review changes, and reproduce issues to verify root-cause fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with a four-phase approach to identify, analyze, and fix root causes before implementing changes.

Core Features & Use Cases

  • Phase-driven debugging: collect symptoms, trace code paths, and verify root causes through hypothesis testing.
  • Deterministic reproduction: reproduce failures reliably to confirm root cause and validate fixes.
  • Structured reporting: produce a clear debug report and escalate when needed to ensure alignment.

Quick Start

Run a structured investigation by listing the symptoms, mapping them to root causes, and following the four phases to verify a fix.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I find the root cause of a bug instead of just patching symptoms?

Root-cause debugging requires collecting symptoms, reviewing recent git changes, and reproducing the issue deterministically. A structured four-phase process of investigation, analysis, hypothesis, and implementation isolates the true origin before you apply a fix.

What is the best way to reproduce a bug reliably for triage?

Deterministic reproduction confirms the root cause by triggering the failure consistently under controlled conditions. Mapping symptoms to code paths and tracing recent changes allows you to reproduce the exact issue state and validate that your fix resolves it.

How do I systematically debug an issue using git history?

Reviewing git changes provides the context needed for triage. By mapping reported symptoms to recent code modifications, you can trace the execution path, form a hypothesis about the root cause, and verify it against a deterministic reproduction.

How do I structure a debug report after investigating a complex issue?

A structured debug report documents the collected symptoms, analyzed code paths, tested hypotheses, and the verified fix. Following a four-phase debugging process ensures the report captures the full triage workflow and includes escalation guidance when needed.

Can I use this debugging approach for any software engineering issue?

Yes, this triage approach applies broadly to software engineering bugs where you can collect symptoms and review code changes. It requires the ability to reproduce the failure deterministically to confirm the root cause and validate the implemented fix through tests.

When should I escalate a bug during root-cause analysis?

You should escalate when the structured debug report indicates the issue exceeds current scope or requires alignment. The debugging process includes clear escalation guidance triggered when hypothesis testing or reproduction efforts hit a wall during the analysis phase.