investigate

Name: investigate
Availability: InStock
Author: yahav123147

Trace failing code paths and validate root-cause hypotheses before implementing fixes.

1|Updated Apr 13, 2026

Search Tags:#debugging #root cause analysis #stack trace #regression #incident response #error investigation

Ready to run

npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill investigate-yahav123147

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/yahav123147/paid-ads-cro-skills/tree/main/skills/investigate
Command: npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill investigate-yahav123147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you stop guessing when something is broken by driving a systematic root-cause investigation so you can fix the underlying issue instead of patching symptoms.

Core Features & Use Cases

Four-phase debugging workflow: investigate, analyze, hypothesize, implement, so you move from evidence to a grounded fix.
Root-cause-first guardrail: enforces the iron law of no fixes without identifying the actual cause.
Best-fit scenarios: debugging when asked to “debug this,” “fix this bug,” “why is this broken,” investigating errors, 500s, stack traces, unexpected behavior, and regressions like “it was working yesterday.”

Quick Start

Ask the skill to investigate your error by giving the exact error message, stack trace, and steps to reproduce, then ask it to produce a root-cause hypothesis and a fix plan that avoids symptom-only changes.

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 500 error or stack trace?▼

To find the root cause of a 500 error or stack trace, this skill drives a four-phase workflow: investigate symptoms, analyze evidence, hypothesize the cause, and implement a grounded fix only after confirming the actual issue.

What is the best way to debug a regression when something was working yesterday?▼

Debugging a regression where code was working yesterday requires tracing the failing code path with search and reads, validating hypotheses through reproduction, and enforcing a no-fix rule until the actual root cause is identified.

How do I systematically investigate unexpected behavior in my software?▼

Systematically investigate unexpected behavior by moving through a structured workflow from evidence to grounded fix: collect symptoms, analyze the failing code path, hypothesize the root cause, and validate it before implementing changes.

Does root cause analysis prevent symptom-only patches during incident response?▼

Yes, root cause analysis enforces an iron law guardrail that blocks symptom-only patches during incident response by requiring you to confirm the actual cause through reproduction and evidence tracing before implementing any fixes.

What information do I need to start debugging an error?▼

To start debugging an error, you need the exact error message, the stack trace, and the steps to reproduce the issue to produce a root-cause hypothesis and a fix plan that avoids symptom-only changes.