systematic-debugger

Diagnose bugs and test failures through four-phase root cause investigation before applying fixes.

Updated Oct 2, 2025
One-click install
npx skills add https://github.com/YuriiYInno/Innogram --skill systematic-debugger-yuriiyinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugger
Source: https://github.com/YuriiYInno/Innogram/tree/main/.codex/skills/systematic-debugger
Command: npx skills add https://github.com/YuriiYInno/Innogram --skill systematic-debugger-yuriiyinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often jump straight to fixes without understanding why a bug occurred, leading to wasted time, recurring issues, and new bugs introduced by guesswork. This Skill enforces a disciplined investigation process that finds the root cause before any fix is attempted. ## Core Features & Use Cases - Four-Phase Debugging Process: Guides root cause investigation, pattern analysis, hypothesis testing, and verified implementation in strict order. - Anti-Thrashing Guardrails: Red-flag detection stops quick-fix impulses and forces a return to systematic investigation when rationalizations appear. - Escalation Logic: After three failed fix attempts, the process flags a potential architectural problem and requires human discussion before continuing. - Use Case: When a test suite fails after a dependency upgrade, use this Skill to read the full stack trace, reproduce the failure, compare against working code, form a single hypothesis, and verify one minimal fix with a failing test case. ## Quick Start Ask the AI to systematically debug the failing test or error you are seeing and find the root cause before proposing any fix.

Frequently Asked Questions about systematic-debugger

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

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

Start by reading the full error message and stack trace, then reproduce the failure consistently. Check recent changes via git diff, trace the bad value to its source, form one hypothesis, and test it with the smallest possible change before implementing a verified fix.

What is root cause analysis in debugging?▼

Root cause analysis identifies the underlying source of a bug rather than treating its symptoms. It involves reading errors carefully, reproducing the issue, tracing data flow to the origin, and confirming a single hypothesis before writing any fix.

When should I stop trying fixes and reconsider the architecture?▼

Stop after three or more failed fix attempts, since repeated failures indicate an architectural problem rather than a simple bug. At that point, discuss the design with a human partner before continuing instead of stacking more changes.

Why do quick fixes without investigation cause more bugs?▼

Quick fixes address symptoms without understanding the cause, so the real issue persists and the change can introduce new defects. Untested fixes also cannot be verified, making it impossible to isolate what actually worked when multiple changes are applied at once.

Can this debugging process handle non-reproducible bugs?▼

Yes, but the first step when a bug is not reproducible is gathering more data rather than guessing at fixes. Consistent reproduction with exact trigger steps is a prerequisite for forming and testing any hypothesis.