skills.rest
jshsakura
jshsakuraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugger

Isolate software bug root causes across code paths using evidence-driven analysis.

22|2|Updated Mar 24, 2026
Search Tags:#debugging#triage#root-cause#software#evidence-based#stack-trace#runtime-state
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill debugger-jshsakura
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/debugger
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill debugger-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently pinpoint root causes of software bugs across code paths, stack traces, and runtime behavior using evidence-based reasoning to reduce repair time.

Core Features & Use Cases

  • Map failure surfaces from trigger to symptom and separate confirmed evidence from hypotheses.
  • Propose minimal, high-impact fixes with explicit validation steps to ensure risk reduction.
  • Provide structured end-to-end analysis that validates normal path, failure path, and integration edge cases.

Quick Start

Isolate the root cause of a bug across code paths by following evidence-driven debugging steps.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I isolate the root cause of a bug across multiple code paths?▼

Isolate the root cause of a bug across code paths by mapping the failure surface from trigger to symptom and separating confirmed evidence from hypotheses to pinpoint the exact failure.

What is evidence-driven debugging and how does it handle stack traces?▼

Evidence-driven debugging applies structured analysis to stack traces and runtime behavior to validate normal and failure paths, ensuring confirmed evidence is separated from hypotheses.

How do I propose minimal software fixes with clear validation steps?▼

Propose minimal software fixes with clear validation steps by applying evidence-based reasoning to isolate high-impact changes, ensuring explicit validation paths and risk reduction.

Can I use this approach for complex debugging tasks involving failing tests?▼

Yes, this approach applies to complex debugging tasks involving failing tests, runtime behavior, and stack traces across modules, providing structured end-to-end analysis to validate integration edge cases.

What is the best way to triage software bugs across different modules?▼

Triage software bugs across different modules by mapping failure surfaces from trigger to symptom, separating confirmed evidence from hypotheses, and validating normal, failure, and edge case paths.

Why does separating evidence from hypotheses help reduce software repair time?▼

Separating evidence from hypotheses reduces software repair time by ensuring structured analysis of runtime state and stack traces, which isolates root causes efficiently and proposes verifiable fixes.

Related Skills

Explore More Software Engineering Skills→
NTCodingNTCoding
334

observability-first-debugging

Instrument software with logs and traces to debug runtime behavior.

Community
Basic
aayushsoamaayushsoam
1

systematic-debugging

Diagnose software errors by enforcing root-cause analysis before applying fixes.

Community
Intermediate
BoraPerusicBoraPerusic

debugger

Diagnose software defects by capturing error messages, reproduction steps, and stack traces.

Community
Intermediate
silva2kandsilva2kand

debug-error

Analyze error messages and stack traces to diagnose root causes and suggest fixes.

Community
Intermediate