investigate

Guide systematic reproduction, analysis, and correction of software failures.

28|3|Updated Jun 13, 2026

Search Tags:#root cause #bug fixing #error analysis #code investigation #systematic analysis

Ready to run

npx skills add https://github.com/AndrewDryga/coop --skill investigate-andrewdryga

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/AndrewDryga/coop/tree/main/internal/scaffold/templates/skills/investigate
Command: npx skills add https://github.com/AndrewDryga/coop --skill investigate-andrewdryga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill assists in identifying the root cause of issues like crashes, panics, failing tests, or incorrect behavior, enabling you to focus on the actual problem rather than mere symptoms.

Core Features & Use Cases

Error Reproduction: Helps you reproduce errors accurately.
Error Analysis: Guides you through reading and understanding error messages in detail.
Root Cause Identification: Leads you to the exact code or data causing the problem.
Minimal Fix Proposal: Suggests the minimal change needed to address the issue.
Regression Testing: Ensures the fix does not introduce new issues.

Quick Start

To investigate a failing test, use the 'investigate' skill with the error message as the argument: 'investigate "error message"'

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 software crash or failing test?▼

To find the root cause of a software crash, you need a systematic process for error reproduction, detailed error message analysis, and code investigation to pinpoint the exact failure. This Skill guides you through these steps to identify the underlying issue.

What is the best way to analyze error messages and fix bugs systematically?▼

Systematic bug fixing involves understanding error messages in detail, reproducing the failure accurately, and tracing the issue to the specific code or data causing the problem. This approach ensures you address the actual problem rather than just treating symptoms.

How do I investigate a software panic without just patching the symptoms?▼

Investigating a software panic requires guiding through error reproduction and root cause identification to locate the exact code triggering the failure. This ensures the minimal fix proposed resolves the core issue rather than masking the panic.

Can I use this systematic analysis if I only have a vague error description?▼

Systematic analysis requires a clear error description and an understanding of the affected codebase to accurately identify and resolve the root cause. Without a precise error message, reproducing the failure and pinpointing the faulty code becomes significantly more difficult.

How do I ensure my bug fix does not introduce new issues into the codebase?▼

To ensure a bug fix does not introduce new issues, you need regression testing to verify the correction does not break existing functionality. This Skill includes proposing a minimal change and validating it through regression testing to prevent new failures.

What is the minimal fix approach for resolving code investigation findings?▼

The minimal fix approach for code investigation findings involves suggesting the smallest possible change needed to address the identified root cause. This prevents unnecessary code modifications while resolving the software failure or panic.