debugger

Diagnose production issues by correlating alerts and logs into root-cause hypotheses.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/dohernandez/claude-skills --skill debugger-dohernandez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/dohernandez/claude-skills/tree/main/plugins/debugger/skills/debugger
Command: npx skills add https://github.com/dohernandez/claude-skills --skill debugger-dohernandez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly diagnosing production issues by correlating alerts with application logs to identify root causes and recommended actions.

Core Features & Use Cases

  • Alert triage: classify alerts by type and affected service to accelerate incident response.
  • Log analysis: search and correlate logs across time windows to surface causal patterns.
  • Root-cause hypothesis: generate evidence-based hypotheses and actionable next steps.

Quick Start

Diagnose a current incident by loading your saved debugger configuration and running a log-and-alert triage.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I diagnose production issues from alerts and logs?

Diagnose production issues by correlating alerts with application logs to identify root causes. The debugger classifies alerts by type and affected service, then searches logs across time windows to surface causal patterns and generate evidence-based hypotheses.

What is the best way to triage alerts across multiple services?

Triage alerts across services by classifying them by type and affected service to accelerate incident response. Pattern-based categorization enables structured debugging, helping you quickly identify which service is impacted and generate actionable next steps.

Can I use custom log commands and environment-specific setup for incident investigation?

Yes, you can use configurable log commands and environment-specific setup for incident investigation. Load your saved debugger configuration to run structured log-and-alert triage tailored to your specific environment and logging infrastructure.

How does log-driven root-cause hypothesis generation work?

Log-driven root-cause hypothesis generation works by searching and correlating logs across time windows to surface causal patterns. These patterns form the basis for evidence-based hypotheses and actionable next steps, accelerating the debugging process.

When do I need pattern-based categorization for alert triage?

You need pattern-based categorization for alert triage when investigating incidents across services. It enables structured debugging by classifying alerts by type and affected service, accelerating incident response and surfacing causal patterns in application logs.