investigate

Guide systematic debugging and root cause analysis of technical bugs.

7|Updated Oct 20, 2025

Search Tags:#code analysis #debugging #root cause analysis #bug hunting #systematic troubleshooting

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill systematically tackles technical debugging with root cause investigation, enabling accurate identification and resolution of bugs.

Core Features & Use Cases

Systematic Approach: Guides users through context detection, root cause investigation, and analysis with evidence tracking.
Performance Debugging: Offers specialized investigation paths for performance bugs.
Environmental Issues: Diagnoses issues related to different environments (local vs. CI/CD).

Quick Start

Start an investigation using 'investigate debug' to begin the root cause analysis of an error.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I perform systematic root cause analysis for a complex software bug?▼

Systematic root cause analysis involves collecting symptoms, reviewing code, and applying investigative phases like data, environment, and performance debugging to accurately identify and resolve technical bugs.

What is the best way to debug performance issues across different environments?▼

Debugging performance issues across environments requires specialized investigation paths that compare local and CI/CD configurations, tracking system metrics and data flow to isolate bottlenecks.

Can I use a systematic troubleshooting approach for environmental issues in CI/CD pipelines?▼

Yes, systematic troubleshooting diagnoses environmental issues by comparing local versus CI/CD configurations, collecting symptoms, and reviewing code to detect discrepancies causing pipeline failures.

How do I start an investigation for a technical bug?▼

Start an investigation by defining the context and collecting symptoms, then proceed through root cause investigation phases while tracking evidence to resolve the technical bug.

What are the limitations of systematic debugging for complex code analysis?▼

Systematic debugging for complex code analysis relies heavily on accurate symptom collection and evidence tracking; incomplete environmental data or obscured performance metrics can hinder root cause identification.