debugger

Guide production incident resolution through a six-step observe-to-verify debugging workflow.

66|16|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/RaheesAhmed/SajiCode --skill debugger-raheesahmed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/RaheesAhmed/SajiCode/tree/main/skills/debugger
Command: npx skills add https://github.com/RaheesAhmed/SajiCode --skill debugger-raheesahmed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging and troubleshooting methodology for production applications. Covers error trace analysis, network debugging, memory profiling, reproducing intermittent bugs, bisecting regressions, stack trace interpretation, log analysis, performance bottleneck identification, and debugging strategies for Node.js, browser, React, and database issues. Use when debugging errors, investigating failures, or troubleshooting performance issues.

Core Features & Use Cases

  • Structured debugging workflow based on a six-step process: Observe, Hypothesize, Test, Isolate, Fix, Verify, with clear criteria and evidence-driven decisions.
  • Error analysis patterns including stack trace interpretation, common error patterns, and practical diagnostic checklists.
  • Real-world use cases across backend services, frontend apps, and data stores, enabling faster incident resolution and dependency-safe fixes.

Quick Start

Diagnose a failing service by observing the exact error, then follow the six-step method to identify, reproduce, and verify a fix.

Frequently Asked Questions about debugger

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

FAQPage Schema
What is a systematic approach for debugging production application failures?

Systematic production debugging uses a structured six-step methodology: observe, hypothesize, test, isolate, fix, and verify. This workflow applies across backend services, frontend apps, and databases to resolve incidents with clear evidence at each stage.

How do I reproduce intermittent bugs in a production environment?

To reproduce intermittent bugs in production, follow the structured debugging workflow by observing exact errors and hypothesizing triggers. The methodology guides you through testing and isolating the root cause using evidence-driven decisions before applying a verified fix.

How do I interpret stack traces and analyze memory leaks in Node.js applications?

Interpreting stack traces and analyzing memory leaks in Node.js applications involves following the six-step debugging workflow. It provides diagnostic checklists for error analysis, performance bottleneck identification, and memory profiling to isolate dependency-safe fixes.

Does this debugging methodology work for both frontend React and database issues?

Yes, this debugging methodology works across frontend React applications and database issues. It provides real-world use cases and error analysis patterns spanning backend services, frontend apps, and data stores for faster incident resolution.

What is the best way to bisect regressions and troubleshoot network errors?

The best way to bisect regressions and troubleshoot network errors is applying a structured debugging workflow. By observing failures, hypothesizing causes, and testing, you can isolate the regression or network issue and verify the fix with concrete evidence.