debugger

Diagnose software issues by collecting symptoms, reviewing logs, and validating root causes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mikebronner/development-settings --skill debugger-mikebronner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/mikebronner/development-settings/tree/main/.ai/skills/debugger
Command: npx skills add https://github.com/mikebronner/development-settings --skill debugger-mikebronner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expert debugger specializing in diagnosing complex software issues, performing root-cause analysis, detecting error patterns, and implementing preventive solutions to accelerate resolution and knowledge transfer.

Core Features & Use Cases

  • Systematic information gathering, log review, and hypothesis formation
  • Error pattern recognition, cascade analysis, and cross-service correlation
  • Production-debugging guidance with non-intrusive checks and thorough documentation

Quick Start

Diagnose the issue by collecting symptoms, reviewing logs, forming hypotheses, and validating the root cause.

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 on cascading failures in distributed systems?

Root-cause analysis for cascading failures in distributed systems requires collecting symptoms, reviewing logs, forming hypotheses, and validating the root cause. This structured elimination approach cross-correlates multi-service errors to pinpoint the originating failure point.

What is the best way to debug intermittent production issues without causing downtime?

Debugging intermittent production issues safely relies on non-intrusive checks and systematic information gathering. By reviewing logs and recognizing error patterns, you can form and test hypotheses without disrupting active multi-service architectures.

How do I diagnose error bursts across multiple services in a log-rich environment?

Diagnosing error bursts across multi-service architectures involves cross-service correlation and cascade analysis. You collect symptoms, review aggregated logs, and apply diagnostic techniques to trace error patterns back to their root cause.

Can I use structured elimination to find the root cause of complex software bugs?

Yes, structured elimination helps find root causes by systematically forming and validating hypotheses against collected symptoms and logs. This methodical diagnostic technique narrows down error patterns to isolate the exact trigger in distributed systems.

What preventive recommendations can I generate after resolving a production bug?

After validating a root cause, you can generate preventive recommendations backed by documented evidence. This ensures knowledge transfer and implements safeguards against similar error patterns or cascading failures recurring in distributed environments.