03 — Debugging & Problem Solving

Apply the scientific method to isolate and fix software defects.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ftnilsson/agent-cli --skill 03-debugging-problem-solving
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 03 — Debugging & Problem Solving
Source: https://github.com/ftnilsson/agent-cli/tree/main/development/skills/03-debugging-and-problem-solving
Command: npx skills add https://github.com/ftnilsson/agent-cli --skill 03-debugging-problem-solving

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers systematically find, isolate, and fix defects in software, transforming debugging from a frustrating chore into a learnable, repeatable process.

Core Features & Use Cases

  • Scientific Method for Debugging: Apply a structured, experimental approach to problem-solving.
  • Isolation Techniques: Learn to use binary search, minimal reproduction, and tracer bullets to pinpoint bugs efficiently.
  • Debugger Proficiency: Master various breakpoint types and effective debugging workflows.
  • Use Case: When a critical bug appears in production, use the principles from this Skill to quickly reproduce the issue, isolate the root cause using binary search on commits, and implement a robust fix with a new test case.

Quick Start

Use the debugging skill to understand how to reproduce a bug by capturing exact conditions and reducing it to the minimum necessary steps.

Frequently Asked Questions about 03 — Debugging & Problem Solving

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

FAQPage Schema
How do I debug code systematically instead of guessing?

Systematic debugging applies the scientific method to problem-solving by reproducing the bug, forming hypotheses, and isolating the root cause using experimental techniques like binary search and minimal reproduction.

What is the best way to isolate a race condition or state mutation bug?

Isolating race conditions and state mutations requires effective use of debuggers, setting specific breakpoints, and adding tracer logging to capture exact execution conditions and pinpoint the mutation source.

How do I reproduce a critical production bug for troubleshooting?

Reproducing a production bug involves capturing the exact environmental conditions and inputs that triggered the defect, then reducing those steps to the minimum necessary actions to consistently replicate the issue locally.

What are common software bug categories I should check during troubleshooting?

Common software bug categories to investigate include off-by-one errors, null reference exceptions, race conditions, unexpected state mutations, and integration mismatches between system components.

How do I find the root cause of a bug using binary search on commits?

Finding a root cause via binary search on commits involves testing historical code versions to identify the exact commit that introduced the defect, then analyzing that specific change to isolate the faulty logic.