debugger

Diagnose software defects by capturing error messages, reproduction steps, and stack traces.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/BoraPerusic/agents --skill debugger-boraperusic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill:  debugger 
Source: https://github.com/BoraPerusic/agents/tree/main/skills/to%20try/debugger
Command: npx skills add https://github.com/BoraPerusic/agents --skill debugger-boraperusic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Core Features & Use Cases

  • Root-cause analysis and reproduction steps
  • Minimal, verifiable fixes with results validation
  • Guided playbook references for complex scenarios

Quick Start

Invoke the debugger with an error description and follow steps to reproduce, isolate the failure location, apply a minimal fix, and verify the outcome.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I perform root-cause analysis for software defects using stack traces?

Root-cause analysis identifies software defects by capturing error messages, reproduction steps, and stack traces to isolate the failure location. You apply a minimal fix and verify the outcome through structured, evidence-based diagnosis across codebases and CI environments.

What is the best way to debug unexpected runtime issues and test failures?

Debugging unexpected runtime issues and test failures involves following guided steps to reproduce the error, isolate the failure location within multi-module projects, apply a minimal verifiable fix, and validate the results to ensure the defect is resolved.

Can I use this debugging approach for multi-module projects and CI environments?

Yes, this debugging approach is applicable to multi-module projects and CI environments, capturing error messages and reproduction steps to resolve unexpected runtime issues and test failures across complex codebases with documented fixes.

How do I reproduce an error and isolate the failure location in my codebase?

To reproduce an error and isolate the failure location, provide an error description to trigger the debugging workflow. This captures stack traces and reproduction steps, guiding you to apply a minimal fix and verify the outcome with validation steps.

Why does my code review process need structured analysis and documented fixes?

Structured analysis and documented fixes ensure evidence-based diagnosis during code review, capturing reproduction steps and stack traces to isolate root causes. This satisfies requirements for verifiable fixes with results validation across multi-module projects.