debugger

Diagnose and fix software bugs through a structured seven-step debugging workflow.

1|Updated Jan 20, 2026

Search Tags:#debugging #documentation #code-quality #step-by-step #reproduction #root-cause-analysis #bug-tracking

Ready to run

npx skills add https://github.com/spenceriam/impulse --skill debugger-spenceriam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/spenceriam/impulse/tree/main/.opencode/skills/debugger
Command: npx skills add https://github.com/spenceriam/impulse --skill debugger-spenceriam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability helps developers systematically identify, reproduce, and resolve bugs by enforcing a disciplined, step-by-step debugging workflow that documents reasoning at every stage.

Core Features & Use Cases

Structured 7-step process: reproduce, isolate, hypothesize, test, fix, verify, and document.
Reproducible results: generates clear, auditable debug outputs and rationales to facilitate collaboration and review.
Safe, auditable fixes: emphasizes minimal changes, traceable reasoning, and robust verification across scenarios.

Quick Start

Describe the bug in detail and I will guide you through steps 1 through 7 to diagnose and fix it.

Frequently Asked Questions about debugger

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

FAQPage Schema

How do I systematically debug and fix software bugs with documented reasoning?▼

Systematic debugging follows a disciplined 7-step workflow: reproduce, isolate, hypothesize, test, fix, verify, and document. This ensures bugs are resolved safely through traceable reasoning and auditable outputs.

What is the best way to reproduce and isolate unexpected behavior in my codebase?▼

Reproducing and isolating unexpected behavior requires a step-by-step process to consistently trigger the issue and narrow down the root cause. This approach generates clear rationales for safe, minimal fixes.

Can I use a structured debugging workflow for failing tests and performance issues?▼

Yes, a structured debugging workflow applies to bug reports, failing tests, unexpected behavior, and performance issues across codebases. It guides thorough reasoning capture to ensure reproducibility and robust verification.

How does root cause analysis ensure safe and auditable code fixes?▼

Root cause analysis ensures safe, auditable fixes by emphasizing minimal changes and traceable reasoning throughout the debugging process. This generates clear outputs that facilitate collaboration and review.

Why should I document reasoning during step-by-step bug tracking?▼

Documenting reasoning during bug tracking enforces thorough capture of diagnostic steps and hypotheses. This creates reproducible results and structured outputs that ensure safety and facilitate code review.