systematic-debugging

Diagnose software bugs through root cause analysis and systematic error investigation.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill systematic-debugging-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/systematic-debugging
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill systematic-debugging-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic Debugging replaces ad-hoc guessing with a repeatable process to reproduce, isolate, diagnose, and verify fixes for software bugs, runtime errors, test failures, and performance regressions. It reduces time-to-resolution by focusing investigation on the true root cause and preventing recurrence through verification and tests.

Core Features & Use Cases

  • Reproduce reliably: Capture clear reproduction steps and environment details to avoid guessing.
  • Isolate efficiently: Use binary-search narrowing, targeted logging, and layer-by-layer checks to pinpoint the failing component, file, function, or line.
  • Diagnose and verify: Parse error messages fully, validate assumptions with concrete checks, implement a corrective change, and add regression tests to prevent recurrence.
  • Use Case: Investigate a production-only "invalid password" login failure by reproducing the error, isolating the backend comparison, discovering hashing-config mismatches, applying a progressive migration fix, and verifying with staged tests.

Quick Start

Run the systematic-debugging skill by providing clear reproduction steps, the full error message, environment details, and any relevant logs to receive a prioritized isolation plan and verification checklist.

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 a runtime exception instead of guessing?

Root cause analysis replaces ad-hoc guessing by using a repeatable process to reproduce, isolate, and diagnose runtime exceptions. It requires clear reproduction steps and environment details to pinpoint exact failing components.

What is the best way to debug intermittent test failures across different service layers?

Systematic debugging isolates intermittent test failures using binary-search narrowing and targeted logging across service layers. It validates assumptions with concrete checks to identify the true source of unexpected behavior.

How do I systematically isolate a performance regression in my application?

To isolate a performance regression, apply layer-by-layer checks and iterative isolation with a debugger. Capturing environment and configuration details allows you to progressively narrow down the bottleneck.

What information do I need to provide to start a systematic bug investigation?

You need to provide clear reproduction steps, the full error message, environment details, and relevant logs. This input generates a prioritized isolation plan and a verification checklist for the bug.

Does systematic debugging help prevent the same software bug from happening again?

Yes, systematic debugging prevents recurrence by implementing corrective changes and adding regression tests. Verifying the fix through testing ensures the original unexpected behavior is fully resolved.

How do I debug a production-only error when I cannot reproduce it locally?

Debug production-only errors by capturing exact environment and configuration details to reproduce the issue remotely. Then isolate the failing component, parse the stack trace, and validate assumptions with concrete checks.