investigate

Identify and resolve software bugs by uncovering their root cause.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/fghaffar/faystack --skill investigate-fghaffar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/fghaffar/faystack/tree/main/investigate
Command: npx skills add https://github.com/fghaffar/faystack --skill investigate-fghaffar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging without understanding the root cause leads to fragile fixes and recurring bugs. This skill guides you through a disciplined, multi‑phase investigation to uncover the true source before any change.

Core Features & Use Cases

  • Phase‑driven workflow: investigation, analysis, hypothesis, implementation.
  • Scope locking: optional freeze to limit edits to the affected module.
  • Pattern library & web search: matches common bugs and suggests known solutions.
  • Safety checks: 3‑strike rule, blast‑radius warnings, and explicit escalation.

Quick Start

Ask the skill to investigate the error you are seeing in your application.

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 bug in my codebase?

To find the root cause of a software bug, you need a systematic investigation workflow that analyzes repository files and git history to uncover the true source before making any changes.

What is the best way to debug unexpected application crashes without causing recurring issues?

The best way to debug unexpected crashes safely is through a multi-phase investigation that includes hypothesis testing and scope locking, which limits edits to the affected module and prevents fragile fixes.

How does systematic debugging use git history and shell tools to resolve errors?

Systematic debugging uses git history and shell tools like grep to perform pattern matching across repository files, guiding investigation, analysis, and safe fixing of the identified root cause.

Can I use web search to help identify and fix common software bugs during an investigation?

Yes, web search can be used during a debugging investigation to match common bugs against a pattern library, suggesting known solutions and aiding the root cause analysis of your codebase.

What safety checks should I apply when modifying code to fix a crash?

When modifying code to fix a crash, apply safety checks like a 3-strike rule, blast-radius warnings, and explicit escalation to ensure changes do not introduce new unexpected behavior.

Do I need access to repository files to investigate the root cause of an error?

Yes, you need access to repository files and git history to investigate the root cause of an error, as these provide the necessary context for systematic investigation and hypothesis testing.