debugger_skill

Overview

This skill performs systematic debugging and root cause analysis to identify and fix software issues efficiently. It combines structured investigation steps, hypothesis-driven testing, and concrete remediation guidance to turn symptoms into lasting fixes. Use it to reduce time-to-resolution and prevent recurrence with tests and monitoring.

How this skill works

The skill inspects error messages, stack traces, logs, environment details, and input data to form prioritized hypotheses. It applies targeted techniques—binary search, isolated repros, strategic logging, breakpoints, and git bisect—to validate causes and locate the faulty code. After identifying the root cause, it prescribes specific fixes, verification steps, and preventive measures.

When to use it

• Investigating crashes, exceptions, or unexpected behavior
• Troubleshooting intermittent or production incidents
• Analyzing stack traces, logs, or crash dumps
• Fixing failing or broken code and regressions
• Validating fixes and adding tests to prevent recurrence

Best practices

• Start by defining expected vs actual behavior and gather reproduction steps
• Collect full context: stack traces, logs, environment versions, and input that triggers the issue
• Form a small set of prioritized hypotheses and test them iteratively
• Use binary search, minimal repro cases, and breakpoints to isolate the fault
• Verify fixes with unit/integration tests and watch for regressions

Example use cases

• Intermittent 500 errors on an API endpoint that occur under load
• A null reference crash after a recent dependency upgrade
• Performance regression introduced by a new deployment
• Off-by-one bug causing array index errors in a loop
• A regression introduced by a commit where git bisect narrows the culprit