debug

Trace data flow to diagnose root cause and apply minimal corrective fix with tests.

6|1|Updated Mar 30, 2026

Search Tags:#debugging #root cause analysis #incident response #test validation #evidence-based #software fixing

Ready to run

npx skills add https://github.com/wesleyosantos91/multi-agents --skill debug-wesleyosantos91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/debug
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill debug-wesleyosantos91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you systematically investigate and resolve a reported software issue by identifying the root cause with evidence and applying the smallest safe fix.

Core Features & Use Cases

Root-cause debugging: Reproduces behavior, traces data flow, and formulates at least two hypotheses validated against code evidence.
Minimal-risk correction: Applies the smallest change that resolves the root cause without refactoring unrelated code.
Validation and reporting: Runs existing tests or creates a minimal test, then documents cause, fix, tests, and residual risk.
Use case: When a bug report describes unexpected behavior, use this skill to turn the report into a verified, test-backed patch.

Quick Start

Ask an AI to run the debug process for the provided error report, including reproduction, evidence-backed hypothesis testing, a minimal fix, and test validation.

Frequently Asked Questions about debug

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

FAQPage Schema

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

To find a software bug's root cause, you reproduce the behavior, trace input-to-output data flow, and formulate at least two evidenced hypotheses validated against code. This systematic diagnosis isolates the actual failure point rather than just treating symptoms.

What is the best way to fix unexpected software behavior reliably?▼

The best way to fix unexpected software behavior reliably is by applying the smallest safe change that resolves the evidenced root cause without refactoring unrelated code. You then validate this minimal correction by running existing tests or creating a minimal test.

How do I validate a software fix without existing tests?▼

You validate a software fix without existing tests by creating a minimal test specifically for the corrected behavior. This test verifies the patch resolves the reported issue and provides a regression check, completing the required validation step.

What should a debugging output report include?▼

A debugging output report should include the identified root cause, the fix rationale, the test validation status, and any residual risk. Documenting these elements ensures the software fixing process is transparent and the incident response is fully traceable.

When should I use evidence-based debugging for incident response?▼

You should use evidence-based debugging for incident response when a bug report describes unexpected behavior and requires a verified, test-backed patch. It is essential when software behavior diverges from expected outputs and demands structured reproduction and diagnosis.