investigate

Guide root-cause debugging through hypothesis testing and regression verification.

10|3|Updated Mar 25, 2026

Search Tags:#debugging #investigation #logging #root-cause #reproduction #phase-analysis #hypothesis-testing

Ready to run

npx skills add https://github.com/olaafrossi/FoamPilot --skill investigate-olaafrossi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/olaafrossi/FoamPilot/tree/main/.claude/skills/investigate
Command: npx skills add https://github.com/olaafrossi/FoamPilot --skill investigate-olaafrossi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root-cause investigation prevents chasing symptoms and accelerates fixes by guiding users through a disciplined, phase-based workflow.

Core Features & Use Cases

Structured four-phase approach: root cause investigation, pattern analysis, hypothesis testing, and implementation, plus verification and learnings.
Reproducible debugging with evidence collection, logging, and regression checks; supports cross-project learnings and proactive guidance.
Use cases include debugging elusive intermittent bugs, regression analysis, and performing post-mortem style investigations with an auditable trail.

Quick Start

Describe the observed symptoms, reproduce the bug if possible, and follow Phases 1 through 5 to identify root cause, test hypotheses, implement fixes, and verify outcomes.

Frequently Asked Questions about investigate

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

FAQPage Schema

What is root-cause debugging and how does it help fix elusive software bugs?▼

Root-cause debugging systematically identifies the underlying origin of software faults rather than treating symptoms. It accelerates fixes by guiding developers through a structured, phase-based workflow covering symptom collection, reproduction, and hypothesis validation.

How do I perform a structured regression analysis when investigating a bug?▼

Perform regression analysis by reproducing the bug deterministically, collecting evidence logs, and validating hypotheses across codebases. Follow structured phases of investigation, pattern analysis, testing, implementation, and verification to isolate faults.

Can I use a phase-based investigation workflow for post-mortem codebase analysis?▼

Yes, phase-based investigation supports post-mortem style reviews by creating an auditable trail. It requires symptom collection, deterministic reproduction, evidence logging, hypothesis validation, and regression testing to produce a structured outcome plan.

What's the best way to reproduce intermittent bugs during software investigation?▼

The best way to reproduce intermittent bugs is to collect observed symptoms and establish deterministic reproduction conditions. Evidence logging and pattern analysis then validate hypotheses before implementing fixes and running regression checks.

Does systematic debugging require evidence logging and hypothesis testing?▼

Yes, systematic debugging requires evidence logging and hypothesis testing to prevent chasing symptoms. This structured approach validates root causes through pattern analysis and regression checks before implementation and verification.