debugging

Diagnose software failures through a five-step reproduce, localize, reduce, fix, and guard workflow.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/OktayCopurlu/ai-shared --skill debugging-oktaycopurlu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/OktayCopurlu/ai-shared/tree/main/.github/workflows/skills/debugging
Command: npx skills add https://github.com/OktayCopurlu/ai-shared --skill debugging-oktaycopurlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When tests fail, builds break, or behavior diverges from expectations, it is tempting to guess at a fix. This Skill enforces a disciplined triage process so you fix the actual root cause instead of symptoms, and every fix ships with a regression test. ## Core Features & Use Cases - Structured 5-Step Triage: Reproduce the failure reliably, localize it with bisection techniques, reduce to a minimal case, fix the root cause, and guard with a regression test. - Isolation Technique Selection: Choose between binary search, input reduction, dependency elimination, git bisect, or targeted logging based on the failure scenario. - Anti-Pattern Guardrails: Built-in tables of common rationalizations and red flags that catch skipped reproduction, repeated blind fix attempts, and fixes committed without tests. - Use Case: A CI pipeline fails after a merge. Use this Skill to reproduce the failure locally, run git bisect to find the offending commit, apply the smallest correct fix, and commit it together with a regression test. ## Quick Start Use the debugging skill to triage this failing test and find the root cause before fixing it.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I debug a failing test systematically?▼

Follow a five-step triage: reproduce the failure reliably, localize it using bisection techniques, reduce it to a minimal case, fix the root cause, and add a regression test. Never skip reproduction, since guessing often fixes the wrong thing.

How to find which commit introduced a bug?▼

Use git bisect to perform a version bisect when a known-good prior state exists. It binary-searches commit history to identify the exact commit that introduced the regression, which is faster than reading the entire codebase.

What techniques isolate a bug in a large codebase?▼

Use binary search by commenting out half the code path, input reduction for data-dependent bugs, dependency elimination for integration issues, git bisect for regressions, or targeted logging at function boundaries to trace execution flow.

Why should I reproduce a bug before fixing it?▼

Fixing without reproduction risks addressing the wrong cause. Reliable reproduction confirms you understand the failure trigger, and it gives you a verifiable exit condition proving the fix actually works.

When should I not use a structured debugging workflow?▼

Skip it when writing new features test-first, which belongs to test-driven development, or when reviewing code that already works, which belongs to code review. This workflow targets active failures and unexpected behavior.