investigate

Trace reported issue symptoms to code paths and verify root cause hypotheses.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill investigate-jonkiky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/jonkiky/ccdi-federation-ai/tree/main/.agents/investigate
Command: npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill investigate-jonkiky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with a disciplined four-phase workflow to reveal root causes before making fixes.

Core Features & Use Cases

  • Four-phase framework: investigate, analyze, hypothesize, implement.
  • Structured evidence gathering: symptoms, logs, traces, and reproductions guide hypotheses.
  • Reproducible debugging: link symptoms to code paths and verify root cause with minimal risk changes.

Quick Start

Initiate a root-cause investigation by collecting symptoms, tracing code paths, and validating hypotheses.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I identify the root cause of a bug from a stack trace?

To identify the root cause of a bug from a stack trace, gather reported symptoms, trace code paths using search tools, and check git history to validate hypotheses before making fixes.

What is the best way to systematically debug a performance regression?

Systematically debug a performance regression by following a four-phase framework: investigate symptoms, analyze logs, hypothesize root causes, and implement minimal risk changes to verify the fix.

How do I reproduce an error and link it to specific code paths?

Reproduce an error by collecting structured evidence like logs and traces, then use grep to search code paths and verify hypotheses linking the observed symptoms to the faulty code.

Can I use git history to investigate the source of a reported issue?

Yes, you can use git history to investigate a reported issue by checking commit logs to trace when symptoms were introduced and linking those changes to the current erroneous code paths.

Does root-cause debugging require reproducing the exact error steps?

Root-cause debugging relies on reproducing exact error steps to gather structured evidence, ensuring hypotheses accurately link observed symptoms to code paths before implementing fixes.

Why should I trace symptoms to code before implementing a bug fix?

Tracing symptoms to code before implementing a bug fix ensures you identify the actual root cause through structured evidence, preventing incorrect patches and reducing the risk of regressions.