debugging_methodology

Guides systematic debugging through reproduce, isolate, hypothesize, and fix phases.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill debugging-methodology-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging_methodology
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/debugging_methodology
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill debugging-methodology-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging often devolves into random guesswork and unverified fixes. This Skill enforces a structured, scientific debugging cycle so errors are reproduced, root-caused, and fixed with verifiable evidence instead of trial and error. ## Core Features & Use Cases - Structured Debugging Cycle: Follows the REPRODUCE → UNDERSTAND → ISOLATE → HYPOTHESIZE → TEST → FIX → REFLECT loop with templates for reproduction reports and hypothesis tables. - Root Cause Analysis Tools: Includes the 5 Whys technique and git bisect binary search to locate the exact commit that introduced a regression. - Three-Phase Workflow: Covers incident triage, root cause analysis, and resolution with post-mortem checkpoints including TDD verification. - Use Case: When a login feature breaks in production, use this Skill to reproduce the error, run git bisect to find the offending commit, rank hypotheses by probability, and ship a minimal verified fix with a regression test. ## Quick Start Use the debugging methodology skill to systematically diagnose why the login endpoint returns a 401 error and produce a verified fix.

Frequently Asked Questions about debugging_methodology

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

FAQPage Schema
How do I debug a bug systematically instead of guessing?

Follow the cycle: reproduce the error with documented steps, isolate the failing component, list hypotheses ranked by probability, then test each one. Write a failing test before applying the fix to verify the root cause.

How to find which commit introduced a bug with git bisect?

Run git bisect start, mark the current commit as bad and a known working commit as good, then let git binary-search the history. You can automate it with git bisect run npm test to test each commit automatically.

What is the 5 Whys technique in root cause analysis?

The 5 Whys technique repeatedly asks why a problem occurred to peel back symptom layers until reaching the root cause. For example, a login failure traces from a 401 error down to an expired token and a changed refresh endpoint.

Why does a bug work locally but fail in production?

Environment differences between development and production, such as versions, configuration, or data, cause this classic trap. The triage phase requires checking version differences and reproducing the error in a matching environment before hypothesizing.

When should I write a post-mortem after fixing a bug?

Write a post-mortem after every verified fix, answering why the bug happened and how to prevent recurrence. Also scan whether similar errors exist elsewhere in the codebase before closing the incident.