debugger

Diagnoses software bugs and system failures from root cause to fix with regression tests.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Exia-thd/Digital-Nervous --skill debugger-exia-thd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/Exia-thd/Digital-Nervous/tree/main/skills/debugger
Command: npx skills add https://github.com/Exia-thd/Digital-Nervous --skill debugger-exia-thd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic identification and resolution of software bugs, crashes, intermittent failures, and performance regressions by guiding triage, evidence collection, hypothesis testing, and verified fixes so teams stop guessing and ship reliable code.

Core Features & Use Cases

  • Triage & Symptom Collection: Classifies severity, gathers error messages, reproduction steps, recent commits, and test failures to form a clear symptom summary.
  • Hypothesis-driven Investigation: Generates ranked hypotheses, runs parallel investigations (code reading, binary search, minimal repro, log analysis, state inspection), and records structured evidence for each hypothesis.
  • Fix Implementation & Verification: Produces minimal, codebase-conforming fixes with regression tests, runs verification checklists, and ensures no side effects before closing the loop.
  • Brownfield & Production Awareness: Prioritizes reading existing tests and logs, preserves patterns, and mandates regression tests for every fix.
  • Outputs: Investigation report, root-cause analysis summary, evidence artifacts, and a regression test placed in the tests/regression/ directory.

Quick Start

Use the debugger to triage the failing test tests/unit/auth.test.ts and produce a root-cause report with a minimal fix and an accompanying regression test.

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 intermittent production errors in a brownfield codebase?

To find the root cause of intermittent production errors, the debugger guides triage by gathering logs, git history, and reproduction steps to form a symptom summary for hypothesis-driven investigation.

What is the best way to triage failing tests and investigate performance regressions?

The best way to triage failing tests and performance regressions is to classify severity and run parallel investigations using code reading, binary search, and log analysis to record structured evidence.

How do I fix software bugs without introducing side effects in existing code?

To fix software bugs without side effects, produce minimal codebase-conforming fixes, add regression tests in the tests/regression/ directory, and run verification checklists before closing the loop.

Can I use git history to diagnose crashes and identify recent commits causing test failures?

Yes, you can use git history to diagnose crashes by gathering recent commits during triage, enabling binary search to isolate regressions and verify hypotheses against source code.

Does root-cause analysis require access to source code and test suites to verify fixes?

Yes, root-cause analysis requires access to source code, test suites, logs, and git history to run tests, apply minimal fixes, and generate an investigation report with evidence artifacts.

What should I do when my software bug investigation is not working and I am just guessing at fixes?

When software bug investigation is not working and you are guessing, stop and use hypothesis-driven investigation to generate ranked theories, collect evidence, and verify minimal fixes with regression tests.