debugging

Reproduce, isolate, and diagnose code failures with evidence-based techniques.

4|Updated Feb 1, 2026

Search Tags:#testing #debugging #code-analysis #reproducibility #root-cause #git-bisect

Ready to run

npx skills add https://github.com/mkalkere/agent-coordinator --skill debugging-mkalkere

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/mkalkere/agent-coordinator/tree/main/.os/skills/development/debugging
Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill debugging-mkalkere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable approach to debugging code failures, enabling agents to reproduce, isolate, diagnose, and verify fixes with evidence.

Core Features & Use Cases

Reproduce errors with exact messages, stack traces, and environment details to establish a reliable failure baseline.
Isolate root causes using systematic techniques and collect corroborating evidence to support conclusions.
Verify fixes through targeted regression checks and documentation to prevent recurrence across projects.

Quick Start

Describe your symptom and environment when you invoke debugging to begin the analysis.

Frequently Asked Questions about debugging

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

FAQPage Schema

How do I systematically debug code failures and isolate root causes?▼

To debug code failures systematically, reproduce the exact error and environment to establish a baseline, then isolate root causes using binary search, input reduction, and git bisect while validating hypotheses with evidence.

What is the best way to reproduce errors for reliable debugging?▼

Reproducing errors for reliable debugging requires capturing exact error messages, stack traces, and environment details to establish a consistent failure baseline before attempting root cause isolation.

How does git bisect work for finding the commit that introduced a bug?▼

Git bisect works for finding bugs by performing a binary search through commit history, systematically isolating the specific code change that introduced the failure while validating each step with evidence.

How do I verify a code fix and prevent regression after debugging?▼

Verify a code fix and prevent regression by applying a minimal correction, running targeted regression checks to confirm the failure is resolved, and documenting findings to prevent future recurrence.

Can I use this debugging approach for any programming language or environment?▼

Yes, this debugging approach applies systematic isolation techniques like binary search and input reduction that are language-agnostic, relying on reproducible failure baselines and evidence validation across any environment.

Why should I use input reduction when diagnosing a code failure?▼

Input reduction should be used when diagnosing code failures because it systematically minimizes the triggering conditions, making it easier to isolate the exact root cause and validate hypotheses with corroborating evidence.