interrogation-debugging

Identify root causes of bugs through a structured multi-phase interrogation workflow.

71|9|Updated Apr 13, 2026

Search Tags:#workflow #debugging #investigation #triage #root-cause #software

Ready to run

npx skills add https://github.com/kucherenko/gangsta --skill interrogation-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interrogation-debugging
Source: https://github.com/kucherenko/gangsta/tree/main/skills/interrogation-debugging
Command: npx skills add https://github.com/kucherenko/gangsta --skill interrogation-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging enforces root-cause investigation before fixes, preventing symptom-based patches and speeding up long-running issues.

Core Features & Use Cases

Structured multi-phase workflow (The Brief, Cross-Examination, The Theory, The Hit) to guide investigation.
Evidence-first debugging with reproducible steps, data gathering, and traceability.
Broad applicability across bugs, test failures, production issues, and performance problems.

Quick Start

To begin, follow the Brief to read errors, reproduce the issue, and gather evidence before proposing changes.

Frequently Asked Questions about interrogation-debugging

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

FAQPage Schema

What is root-cause debugging and when do I need a structured investigation workflow?▼

Root-cause debugging identifies the true source of software bugs, test failures, and unexpected behavior before applying fixes. You need a structured investigation workflow to prevent symptom-based patches and speed up long-running production issues.

How do I debug test failures and production issues using a multi-phase interrogation workflow?▼

Debug test failures and production issues by following structured phases: The Brief to read errors and reproduce, Cross-Examination to gather evidence, The Theory to hypothesize, and The Hit to implement traceable fixes.

Can I use this structured debugging workflow for CI pipeline failures and performance problems?▼

Yes, the structured debugging workflow applies broadly across CI pipeline failures, performance problems, and production issues, enabling reproducible investigation and traceable fixes regardless of the software project environment.

What's the best way to investigate bugs without applying symptom-based patches?▼

The best way to investigate bugs without symptom-based patches is enforcing evidence-first debugging, gathering reproducible data and steps before proposing changes, and escalating only when structured interrogation fails to reveal the root cause.

Why does my debugging process fail to find the true root cause of unexpected software behavior?▼

Debugging often fails to find the root cause when it skips evidence gathering and reproducible steps, jumping directly to fixes. A structured interrogation workflow enforces data traceability and root-cause identification before changes.

What are the limitations of structured debugging workflows for triaging software issues?▼

Structured debugging workflows require gathering evidence and reproducing issues before proposing changes, which may slow down immediate symptom relief. However, this constraint prevents symptom-based patches and ensures traceable fixes for complex bugs.