skills.rest
zhaono1
zhaono1COMMUNITY
Explore all skills by this author →
GitHub

debugger

Guide structured debugging from error identification to verified fixes.

69|11|Updated Jan 10, 2026
Search Tags:#debugging#logging#code#errors#reproduction#root-cause-analysis
One-click install
npx skills add https://github.com/zhaono1/agent-playbook --skill debugger-zhaono1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/zhaono1/agent-playbook/tree/main/skills/debugger
Command: npx skills add https://github.com/zhaono1/agent-playbook --skill debugger-zhaono1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Advanced debugging specialist that helps diagnose and resolve code issues systematically.

Core Features & Use Cases

  • Understand, isolate, analyze, and fix bugs with a structured debugging process.
  • Helps reproduce errors from logs and stack traces, suggests fixes, and provides verification steps.
  • Use Case: When a user reports a bug, the skill guides through root cause analysis and recommended changes.

Quick Start

Describe the error and any relevant context, and I will guide you through reproduction, isolation, analysis, and a recommended fix.

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 runtime error from a stack trace?▼

To find the root cause of a runtime error from a stack trace, provide the error details and contextual code to enable root-cause analysis. This guides you through isolating the issue and verifying the recommended fix.

What is the best way to systematically debug logical bugs in production code?▼

The best way to systematically debug logical bugs in production code is to follow a structured workflow from error identification to verified fixes. This requires gathering logs and contextual code information to propose accurate reproduction steps and fixes.

Can I use a systematic debugging workflow for syntax issues across different programming languages?▼

Yes, you can use a systematic debugging workflow for syntax issues across different programming languages. The process works across project types and languages by guiding you through error identification, root-cause analysis, and fix recommendations.

How do I reproduce an error when I only have limited logs and contextual code?▼

To reproduce an error with limited logs, you must analyze the available error details and stack traces to infer the execution path. This allows you to propose specific reproduction steps that trigger the same logical bug or runtime failure.

What do I need to start diagnosing code issues in a staging environment?▼

To start diagnosing code issues in a staging environment, you need access to error details, logs, and contextual code information. These inputs enable the structured workflow to move from error identification through root-cause analysis to verified fixes.

Related Skills

Explore More Software Engineering Skills→
odylithodylith
34

odylith-casebook-bug-capture

Create Casebook bugs with grounded repro details for Odylith failures.

Official
Intermediate
samChang72samChang72
1

test-fixing

Group failing test errors by type and guide fixes.

Community
Intermediate
tilework-techtilework-tech
149

Root-Cause-Tracing

Trace backward through call stacks to locate a bug's original trigger.

Official
Intermediate
Neuron-Mr-WhiteNeuron-Mr-White
56

debug

Reproduce and diagnose software bugs with a structured debug report.

Community
Intermediate