systematic-debugging

Trace failures through logs and call chains to identify root causes before fixing.

Updated Jan 26, 2026

Search Tags:#debugging #root cause #troubleshooting #test failures #bug analysis #failure investigation

Ready to run

npx skills add https://github.com/idoberk/BoQAppFront --skill systematic-debugging-idoberk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/idoberk/BoQAppFront/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/idoberk/BoQAppFront --skill systematic-debugging-idoberk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill stops guess-and-check debugging by forcing a root-cause-first investigation before any fix is proposed, reducing wasted time, regression risk, and repeated failures.

Core Features & Use Cases

Four-phase workflow: Guides debugging through investigation, pattern analysis, hypothesis testing, and implementation.
Pressure-resistant guardrails: Prevents shortcut fixes when the issue seems simple, urgent, or already partially diagnosed.
Root-cause tracing: Helps trace failures backward through logs, stack traces, and call chains to identify the original trigger.
Validation and recovery: Encourages minimal tests, evidence gathering, and architectural review after repeated failed attempts.
Use case: Apply it when a build fails, a test becomes flaky, production behavior is unexpected, or an initial fix did not work.

Quick Start

Use the systematic-debugging skill to investigate the bug from root cause to verified fix before proposing any changes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of flaky test failures instead of guessing?▼

Root cause debugging prevents guess-and-check cycles by requiring evidence gathering, pattern comparison, and single-hypothesis testing before any fix is attempted. It traces failures backward through logs and stack traces to identify the original trigger.

What is the best way to debug multi-component production incidents?▼

Systematic debugging handles multi-component production incidents through a four-phase workflow: investigation, pattern analysis, hypothesis testing, and implementation. It applies pressure-resistant guardrails to prevent shortcut fixes when issues seem urgent.

How do I troubleshoot build issues without introducing regressions?▼

Troubleshoot build issues without regressions by validating fixes with minimal tests and gathering evidence before implementation. When repeated attempts fail, an architectural review prevents regression risk and reduces wasted time.

Why does my quick patch for unexpected production behavior keep failing?▼

Quick patches for unexpected production behavior fail because they bypass root-cause tracing. Without testing a single hypothesis and tracing the original trigger through call chains, the underlying failure remains unresolved and regression risk increases.

When do I need systematic bug analysis for test failures?▼

You need systematic bug analysis for test failures when quick patches are tempting, initial fixes do not work, or behavior is flaky. It enforces pressure-resistant guardrails to ensure root-cause-first investigation before any verified implementation.