debugger

Diagnose software bugs from errors, stack traces, logs, and failing tests.

2|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/rakibulism/agent-skills-os --skill debugger-rakibulism
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/rakibulism/agent-skills-os/tree/main/skills/debugger
Command: npx skills add https://github.com/rakibulism/agent-skills-os --skill debugger-rakibulism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose software failures from error messages, stack traces, logs, or reproducible bad behavior. It focuses on identifying the real root cause so you can fix the issue instead of masking it.

Core Features & Use Cases

  • Root-cause analysis: Turns vague failures into a precise symptom, likely cause, and supporting evidence.
  • Minimal verification: Suggests the cheapest test to distinguish between competing hypotheses.
  • Concrete fixes: Recommends a specific code change and a follow-up verification step, usually a failing test.
  • Use case: A test suddenly starts failing after a refactor; this Skill helps determine whether the problem is null data, off-by-one logic, stale state, environment mismatch, or another common failure pattern.

Quick Start

Ask the debugger skill to analyze the error message, relevant code, and reproduction steps, then provide the likely root cause and the smallest test that confirms it.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I find the root cause of a software bug from a stack trace?

To find the root cause of a software bug from a stack trace, you restate the precise symptom, formulate ranked hypotheses, and run minimal verification tests to isolate the actual failure point across your codebase.

What is the best way to troubleshoot a failing test after a code refactor?

The best way to troubleshoot a failing test after a refactor is to analyze the reproduction steps and logs to distinguish whether the regression stems from null data, off-by-one logic, stale state, or an environment mismatch.

How do I diagnose an unexpected output error without just masking the symptom?

To diagnose an unexpected output error without masking the symptom, identify the underlying root cause by analyzing logs and runtime behavior, then apply a specific code change validated by a test that fails before the fix.

Can I use systematic debugging for crash analysis across different runtime environments?

Yes, you can use systematic debugging for crash analysis across different runtime environments by restating the precise symptoms and applying minimal verification to test ranked hypotheses regardless of the specific platform.

Why does my regression debugging process need a validation test that fails beforehand?

Regression debugging requires a validation test that fails beforehand to confirm the identified root cause is accurate and ensure the specific code change actually resolves the original software failure.

What is the minimal verification needed to distinguish between competing bug hypotheses?

Minimal verification involves running the cheapest possible test to distinguish between competing bug hypotheses, allowing you to quickly isolate the root cause without performing extensive diagnostic overhead.