debugging

Diagnose bugs by enforcing root-cause investigation before code changes.

Updated Apr 19, 2026

Search Tags:#debugging #verification #diagnostics #root-cause #reproduction #bug-analysis #stack-trace

Ready to run

npx skills add https://github.com/saranskumar/anti-slop --skill debugging-saranskumar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/saranskumar/anti-slop/tree/main/skills/debugging
Command: npx skills add https://github.com/saranskumar/anti-slop --skill debugging-saranskumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bugs don't lie — but they do mislead. Guessing at a fix before understanding the root cause makes things worse. This skill forces systematic diagnosis before any code changes.

Core Features & Use Cases

Read and interpret error messages and stack traces to identify symptom vs. root cause.
Reproduce failures consistently to establish reliable failure modes.
Isolate failure points with guided, step-by-step reasoning and verification.
Validate fixes by confirming the root cause is addressed and related functionality remains healthy.
Reference best practices and example scenarios to accelerate debugging across languages and frameworks.

Quick Start

Provide the exact error message and stack trace, reproduce the bug reliably, identify the root cause, and propose a verified fix.

Frequently Asked Questions about 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 error from a stack trace?▼

Systematic root-cause investigation requires reading the stack trace to distinguish symptoms from the actual failure point, reproducing the error consistently, and isolating the exact code path before applying any changes.

What is the best way to debug intermittent test failures and crashes?▼

The best way to debug intermittent failures is to establish a reliable reproduction sequence, capture clear error states during the crash, and isolate the specific race condition or state corruption through guided step-by-step verification.

How do I systematically diagnose a bug before changing any code?▼

Systematically diagnose a bug by enforcing structured debugging discipline: read error messages, reproduce the failure mode, isolate the root cause through verification, and document the process to ensure the fix addresses the core issue.

Can I use this debugging process across different languages and frameworks?▼

Yes, the debugging process applies to runtime errors, failed tests, and crashes across software projects regardless of language, using structured debugging discipline and best practice scenarios to accelerate diagnosis.

Why should I reproduce a bug consistently before attempting a fix?▼

Reproducing a bug consistently establishes a reliable failure mode, which is necessary to isolate the exact failure points and verify that your proposed fix actually addresses the root cause rather than masking symptoms.

What should I provide to start a bug analysis?▼

To start a bug analysis, provide the exact error message and stack trace, a reliable method to reproduce the bug, and any relevant test cases to ensure the root cause is identified and the fix is verifiable.