systematic-debugging

Diagnose bugs through a four-phase root cause investigation workflow before proposing fixes.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill systematic-debugging-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill systematic-debugging-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing bugs, test failures, or unexpected behavior, it is tempting to jump straight to a quick fix without understanding the root cause, which leads to stacked patches, recurring issues, and wasted effort. This Skill enforces a disciplined investigation process so fixes address the actual source of the problem. ## Core Features & Use Cases - Four-Phase Debugging Process: Root cause investigation, pattern analysis, hypothesis testing, and verified implementation, with each phase gating the next. - Red Flag Detection: Stops and returns to investigation when it catches guessing behaviors like "quick fix for now" or stacking multiple changes at once. - Escalation Path: After three failed fix attempts, it stops and escalates with evidence instead of continuing to guess. - Use Case: A test suite fails after a dependency update. Instead of tweaking assertions, the Skill traces recent changes with git log, reproduces the failure, compares against working code, forms a single hypothesis, and verifies one minimal fix. ## Quick Start Use the systematic-debugging skill to investigate why the login test is failing before suggesting any fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I debug a test failure without guessing at fixes?▼

Follow a four-phase process: investigate the root cause by reading errors and reproducing the issue, analyze patterns against working code, test one hypothesis at a time, then implement and verify a single fix. Never propose fixes before completing the investigation phase.

What is root cause analysis in software debugging?▼

Root cause analysis traces a bug to its origin rather than patching symptoms. It involves reading stack traces completely, reproducing the issue reliably, checking recent changes with git log and git diff, and tracing bad data back to its source.

How do I debug issues in multi-component systems?▼

Log what enters and exits each component boundary, then run the system once to gather evidence showing where the flow breaks. Investigate the failing component specifically instead of guessing across the whole system.

When should I stop trying fixes and escalate a bug?▼

Stop after three failed fix attempts. Continuing to stack changes usually means the underlying architecture or assumption is wrong, so escalate to the project owner with the evidence gathered during investigation.

Why do quick fixes make debugging harder?▼

Quick fixes applied without investigation mask the real cause, stack on top of each other, and make the issue harder to reproduce and isolate. Signs include changing multiple things at once or proposing solutions before tracing the data flow.