debug

Guide investigation-first debugging to identify root causes in software projects.

24|3|Updated Feb 22, 2026

Search Tags:#automation #debugging #investigation #handoff #root-cause #regression-test #trace-analysis

Ready to run

npx skills add https://github.com/Borda/AI-Rig --skill debug-borda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Borda/AI-Rig/tree/main/plugins/develop/skills/debug
Command: npx skills add https://github.com/Borda/AI-Rig --skill debug-borda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through investigation-first debugging to surface the true root cause by collecting evidence, tracing data flow, and formulating a confirmed hypothesis before writing regression tests.

Core Features & Use Cases

Investigation-first data gathering: collect signals, logs, and traces to define a verifiable hypothesis.
Regression test planning: write a regression test or test scaffolding to validate the fix.
Structured handoff: hand off to fix mode with a documented diagnosis and scope.

Quick Start

Describe a failing symptom, gather evidence, and form a root-cause hypothesis for debugging.

Frequently Asked Questions about debug

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

FAQPage Schema

What is the best way to find the root cause of a software bug instead of just patching symptoms?▼

Root-cause debugging uses an investigation-first workflow to collect evidence, trace data flow, and formulate a confirmed hypothesis before writing code, ensuring the true source of the software problem is surfaced rather than just treating symptoms.

How do I structure a debugging investigation when facing a complex test failure?▼

To debug a complex test failure, you collect signals and logs to define a verifiable hypothesis, perform trace analysis, and prepare regression-test scaffolding to validate the fix while ensuring safety and reproducibility before handoff to fix mode.

When do I need trace analysis and data-flow tracing during software debugging?▼

Trace analysis and data-flow tracing are needed when a failing symptom lacks an obvious cause, requiring you to gather execution signals and map data movement across the project to build a confirmed root-cause hypothesis.

How do I hand off a confirmed bug diagnosis to a fix workflow safely?▼

You hand off a confirmed bug diagnosis safely by documenting the investigation scope and root-cause hypothesis, specifying requirements for tools and steps, and preparing regression tests to ensure the fix mode is reproducible.

Does investigation-first debugging work for general software projects and automated workflows?▼

Investigation-first debugging applies across general software projects, automated workflows, and test failures by guiding evidence gathering and trace analysis to surface the root cause before transitioning to fix mode.

Why write a regression test before fixing a bug identified during root-cause investigation?▼

Writing a regression test before fixing a bug validates the diagnosis, ensures the identified root-cause hypothesis is accurate, and provides scaffolding to confirm the fix resolves the issue without introducing new regressions.