debugger

Reproduce, explain, and verify bugs to identify root causes.

2|Updated Jun 3, 2021
One-click install
npx skills add https://github.com/kalindudc/shell --skill debugger-kalindudc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/kalindudc/shell/tree/main/home/.config/opencode/skills/debugger
Command: npx skills add https://github.com/kalindudc/shell --skill debugger-kalindudc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigating bugs is made systematic by reproducing failures, explaining code behavior in plain language, forming and ranking hypotheses, gathering evidence, and verifying root causes before suggesting fixes.

Core Features & Use Cases

  • Reproduce failures with concrete scripts or commands to demonstrate the issue.
  • Explain failure points clearly by narrating what the code does at the failure.
  • Form and rank 1-3 hypotheses, define evidence to confirm or refute each, and pursue the highest-confidence path first.
  • Gather evidence from logs, diffs, and test results and compile a concise handoff report.

Quick Start

Reproduce the reported bug with a minimal script or command and begin documenting findings.

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 bug in my codebase?

Finding the root cause of a bug involves reproducing the failure with a minimal script, explaining the code behavior at the failure point, forming ranked hypotheses, and gathering evidence from logs and diffs to verify conclusions.

What is the best way to structure a debugging investigation?

The best way to structure a debugging investigation is to follow a scientific workflow: reproduce the reported bug, explain the failure in plain language, form 1-3 ranked hypotheses, gather evidence to confirm or refute them, and compile a concise report.

Can I use a structured debugging workflow for incident investigations and code reviews?

Yes, you can use a structured debugging workflow for incident investigations and code reviews across languages and environments. It helps reproduce failures, explain code behavior, and verify root causes systematically before applying fixes.

How do I form and rank hypotheses during a bug investigation?

To form and rank hypotheses during a bug investigation, identify 1-3 potential root causes, define the evidence needed to confirm or refute each one, and pursue the highest-confidence path first using logs, diffs, and test results.

What evidence do I need to verify root causes before suggesting code fixes?

To verify root causes before suggesting code fixes, you need to gather evidence from logs, diffs, and test results. This evidence confirms or refutes your ranked hypotheses and supports a concise handoff report of the verified conclusions.