investigate

Diagnose software issues by proposing hypotheses, running experiments, and generating reports.

Updated May 16, 2026

Search Tags:#debugging #root cause analysis #experimentation #diagnostic report #issue diagnosis

Ready to run

npx skills add https://github.com/korchasa/flowai-plugins --skill investigate-korchasa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/korchasa/flowai-plugins/tree/main/plugins/flowai/skills/investigate
Command: npx skills add https://github.com/korchasa/flowai-plugins --skill investigate-korchasa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of diagnosing issues and identifying root causes, saving time and reducing the complexity of debugging.

Core Features & Use Cases

Autonomous Issue Diagnosis: Automatically propose and test hypotheses to diagnose issues.
Experiment-Based Analysis: Run experiments to validate hypotheses and refine probabilities.
Diagnostic Report Generation: Produce a report with recommended fixes without applying them.
Use Case: When you encounter a failing behavior or a bug, use this Skill to quickly identify the root cause and receive a report with a proposed fix.

Quick Start

Use the investigate skill to diagnose the issue with the error message 'Error: Failed to load module'.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I automate issue diagnosis and root cause analysis for debugging?▼

Automated issue diagnosis works by proposing hypotheses, running experiments to test them, and generating a diagnostic report with recommended fixes. This streamlines debugging workflows by refining probabilities based on experiment results without applying changes.

What is the best way to diagnose a software bug through experiment-based analysis?▼

Experiment-based analysis validates hypotheses by running targeted scripts, interpreting the results, and refining the probability of each potential root cause. This methodical approach ensures accurate issue diagnosis before proposing any fixes.

Can I generate a diagnostic report with recommended fixes without automatically applying them?▼

Yes, the root cause analysis process produces a diagnostic report containing recommended fixes without applying them. This allows you to review the proposed solutions for your software issue safely before making any changes.

How do you identify a root cause when you encounter a failing behavior or software bug?▼

To identify a root cause, the diagnostic process proposes potential hypotheses, executes experiments to validate them, and interprets the results. It then narrows down the failing behavior to a specific root cause and generates a report with a proposed fix.

Do I need the ability to execute scripts to run hypothesis testing for issue diagnosis?▼

Yes, autonomous issue diagnosis requires the ability to execute scripts and interpret their results. This experiment-based analysis validates hypotheses and refines root cause probabilities dynamically during the debugging workflow.

When should I use an automated diagnostic report for software debugging instead of manual analysis?▼

Automated diagnostic reports are ideal when you encounter a failing behavior and need to quickly identify the root cause. It saves time and reduces debugging complexity by autonomously proposing hypotheses and testing them.