debug

Diagnose bugs and test failures through evidence-based root cause investigation before fixing.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill debug-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/sandsower/beislid/tree/main/skills/debug
Command: npx skills add https://github.com/sandsower/beislid --skill debug-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing bugs, test failures, or unexpected behavior, it is tempting to guess at fixes or apply quick patches without understanding the underlying issue. This Skill enforces a disciplined debugging methodology that requires identifying the root cause with evidence before any code changes are proposed, preventing wasted effort and recurring defects. ## Core Features & Use Cases - Hard Gate on Fixes: Blocks any fix proposal until the root cause is identified with concrete evidence, eliminating shotgun debugging. - Four-Phase Method: Guides a structured workflow of reproduce, investigate, hypothesize, and fix, including writing a failing test before implementing the fix. - Red Flag Detection: Surfaces common anti-patterns like "let me just try changing X" or "quick fix for now" and redirects back to investigation. - Use Case: A test suite suddenly fails after a refactor. Instead of tweaking assertions, the Skill walks through checking recent git changes, tracing data flow to the failure point, forming a single testable hypothesis, and only then writing a regression test and fix. ## Quick Start Use the debug skill to investigate why the login integration test is failing and find the root cause before proposing any fix.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a test failure without guessing?▼

Start by reproducing the failure consistently and reading the full stack trace. Then investigate recent changes with git log and git diff, trace the data flow to the error point, and form one evidence-based hypothesis before attempting any fix.

What is root cause analysis in debugging?▼

Root cause analysis identifies the actual source of a bug rather than its symptoms. This Skill enforces it as a hard gate: no fix may be proposed until the root cause is supported by concrete evidence, not assumptions like "it's probably X".

How to debug issues in multi-component systems?▼

Isolate which component fails first by tracing the data flow from input to the error point across component boundaries. Find a working reference point where the system last behaved correctly and identify what changed since then.

What should I do when stuck debugging a bug?▼

If three hypotheses have been tested and disproved, stop and explicitly state that you do not understand the issue yet, then surface it to the user. Continuing to guess at that point produces unreliable fixes and wastes effort.

Why write a failing test before fixing a bug?▼

A failing test captures the exact bug behavior and proves the fix works when it turns from red to green. It also acts as a regression test, and running the full suite afterward confirms the fix did not break anything else.