One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill debugger-code-saurabh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/debugger
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill debugger-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents symptom-based patching by guiding systematic investigation to identify and confirm the precise root cause of bugs, crashes, failing tests, performance regressions, and unexpected behavior.

Core Features & Use Cases

  • Four-Phase Investigation: Move through investigation, analysis, hypothesis testing, and implementation in a disciplined order.
  • Evidence-Based Diagnosis: Reproduce issues, inspect environments, trace data flow, analyze logs, rank hypotheses, and validate causes with falsifiable tests.
  • Production-Grade Resolution: Require regression tests, minimal fixes, target-environment verification, root-cause documentation, monitoring review, and escalation after three unsuccessful fix attempts.
  • Use Case: When an API intermittently returns errors after a deployment, use this Skill to compare environments, trace the request flow, test timing and dependency hypotheses, confirm the root cause, and implement a verified regression-tested fix.

Quick Start

Use the debugger skill to investigate this failing test, identify and confirm its root cause, and propose the smallest verified fix.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I find the root cause of failing tests and unexpected software behavior?

To find the root cause of failing tests, you reproduce the issue, inspect environments, trace data flow, rank falsifiable hypotheses, and validate causes through regression testing before implementing fixes.

What is the best way to investigate intermittent API errors and performance regressions in production?

Investigating intermittent API errors requires comparing environments, tracing request flow, analyzing logs, and testing dependency or timing hypotheses to confirm the root cause before applying production-grade fixes.

How do I stop symptom-based patching when debugging crashes and infrastructure failures?

To stop symptom-based patching during debugging, follow a four-phase investigation moving through evidence-based diagnosis, hypothesis testing, minimal changes, and documented completion criteria to confirm precise causes.

Can I use systematic bug investigation for flaky issues and HTTP failures across development environments?

Yes, systematic bug investigation applies to flaky issues and HTTP failures across development and production environments by requiring reproducible evidence, environment verification, and ranked falsifiable hypotheses.

What should I do if my bug fix attempts keep failing during regression testing?

If bug fix attempts fail during regression testing, escalate after three unsuccessful fix attempts, verify the target environment, review monitoring data, and document the root cause to ensure production-grade resolution.

Does root cause analysis require reproducible evidence before implementing minimal changes?

Yes, root cause analysis requires reproducible evidence and data-flow analysis to validate causes with falsifiable tests, ensuring you implement only minimal changes verified by regression testing.