skills.rest
mattdurham
mattdurhamCOMMUNITY
Explore all skills by this author →
GitHub

debugger

Collect logs and traces to diagnose software issues and write reports to bots/debug.md.

9|3|Updated Feb 8, 2026
Search Tags:#automation#debugging#logs#postmortem#root-cause#bug#stack-trace
One-click install
npx skills add https://github.com/mattdurham/bob --skill debugger-mattdurham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/mattdurham/bob/tree/main/agents/debugger
Command: npx skills add https://github.com/mattdurham/bob --skill debugger-mattdurham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The debugging workflow helps engineers quickly identify, reproduce, and resolve software issues by collecting context, logs, and traces, and by preserving a structured postmortem for prevention.

Core Features & Use Cases

  • Structured debugging workflow: symptom analysis, hypothesis testing, evidence collection, root-cause isolation, and solution validation.
  • Postmortems and knowledge capture: writes comprehensive debugging reports to bots/debug.md for sharing and prevention.
  • On-demand tooling guidance: instructs how to reproduce issues across environments, coordinate with error-detective, qa-expert, and code-reviewer to accelerate resolution.

Quick Start

Begin a debugging session by querying the debugging context, reproducing the issue, analyzing evidence, and writing the comprehensive debugging report to bots/debug.md.

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 using stack traces and logs?▼

Structured debugging collects logs, traces, and environmental data to systematically analyze code paths, reproduce errors, and isolate root causes across diverse environments.

What is the best way to structure a postmortem report after resolving a bug?▼

A structured postmortem captures symptom analysis, hypothesis testing, evidence collection, root-cause isolation, and validation steps, writing comprehensive debugging reports for knowledge transfer and prevention.

Can I use a structured debugging workflow to reproduce errors across different environments?▼

Yes, systematic debugging instructs how to reproduce issues across diverse environments by collecting context, logs, and traces, coordinating with error-detective, qa-expert, and code-reviewer.

How do I prevent recurring software issues after fixing a bug?▼

Generate a comprehensive debugging report with validation steps and prevention measures saved to bots/debug.md, preserving structured postmortems for knowledge transfer and issue prevention.

Do I need any specific tools or dependencies to perform systematic code path analysis?▼

No specific dependencies are required; the workflow collects logs, traces, and environmental data to systematically analyze code paths and isolate root causes without external tooling.

Related Skills

Explore More Software Engineering Skills→
NTCodingNTCoding
334

observability-first-debugging

Instrument software with logs and traces to debug runtime behavior.

Community
Basic
tyhuffman7tyhuffman7
1

investigate

Guide structured four-phase bug investigations to diagnose root causes.

Community
Advanced
TestAny-ioTestAny-io
79

debug

Diagnose Testany test failures by analyzing execution logs and identifying root causes.

Official
Intermediate
fmflurryfmflurry
171

learned-codemap-jump-navigation-angular

Navigate Angular codebases from routes to providers, facades, use-cases, and stores via codemaps.

Community
Intermediate