Verified:GitHub

investigate

Guide engineers through hypothesis-driven root-cause analysis before applying fixes.

Updated Apr 11, 2026

Search Tags:#debugging #investigation #traceability #quality-assurance #root-cause #pattern-analysis #hypothesis-testing

Ready to run

npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill investigate-akiyoshi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root-cause debugging discipline that prevents fix-quick firefighting by requiring evidence-based investigations before changes.

Core Features & Use Cases

Phase-based debugging workflow (Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation, Verification)
Guided tool-assisted analysis with prompts and commands to collect evidence, reproduce issues, and validate fixes
Clear escalation points to avoid scope creep and ensure durable solutions

Quick Start

Start Phase 1 by collecting symptoms and reading the code path to identify the root cause.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I perform systematic root-cause debugging for complex codebase regressions?▼

Hypothesis-driven debugging prevents recurring bugs by requiring evidence collection and root-cause verification before applying fixes. It enforces a phase-based workflow encompassing investigation, pattern analysis, hypothesis testing, implementation, and verification.

What's the best way to stop fix-quick firefighting and ensure traceability during bug investigations?▼

Structured debugging workflows prevent fix-quick firefighting by requiring evidence-based investigations and explicit root-cause verification steps before changes. This enforces traceability and ensures durable solutions across complex systems.

How do I start a structured root-cause investigation when reproducing a feature regression?▼

Start root-cause investigation by collecting symptoms and reading the code path to identify the root cause. Use guided tool-assisted analysis with commands to collect evidence and reproduce issues before forming testable hypotheses.

Does this hypothesis-driven debugging workflow integrate with bash and ask_user tools for evidence collection?▼

Hypothesis-driven debugging integrates with tools like ask_user and bash to facilitate guided tool-assisted analysis. This integration prompts engineers to collect evidence, reproduce issues, and validate fixes during the investigation.

What are the limitations of applying pattern analysis without explicit root-cause verification steps?▼

Applying pattern analysis without explicit root-cause verification risks implementing superficial fixes that fail to address the actual issue. A documented verification workflow, including a regression test, is required to ensure the fix is durable and safe.