debugger

Reproduce software issues and collect logs to verify root causes.

3|Updated Mar 7, 2020

Search Tags:#debugging #logs #evidence #reproduce #triage #root-cause #reproducible

Ready to run

npx skills add https://github.com/qsdrqs/dotfiles --skill debugger-qsdrqs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Provides a structured, evidence-based approach to debugging that ensures reproducible steps, captures commands and logs, avoids guessing, and yields a verified root cause and fix.

Core Features & Use Cases

Reproduce first: reproduce the user-reported issue using exact steps and environmental context.
Collect evidence: capture outputs, stack traces, logs, and relevant files to build an audit trail.
Verify fixes: re-run reproduction and tests to confirm the bug is resolved and document results.

Quick Start

Reproduce the issue with the exact steps and gather logs to identify the root cause.

Frequently Asked Questions about debugger

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

FAQPage Schema

What is evidence-driven debugging and how does it help find a root cause?▼

Evidence-driven debugging is a structured approach that uses exact reproduction steps and captured logs to identify a root cause without guessing. It builds an audit trail from stack traces and outputs to verify the fix and prove the bug is resolved.

How do I debug flaky tests and reproduce intermittent crashes?▼

To debug flaky tests and crashes, reproduce the issue using exact steps and environmental context to capture outputs and stack traces. This evidence collection builds an audit trail to triage the fault and verify the post-fix results.

What's the best way to triage software issues and avoid guessing during debugging?▼

The best way to triage software issues is to follow an intake checklist that captures explicit reproduction steps and logs. This evidence-driven method avoids guessing by documenting an audit trail and verifying the post-fix root cause.

Can I use this approach to debug performance problems and capture relevant logs?▼

Yes, you can use this approach to debug performance problems by capturing relevant logs and outputs during fault reproduction. It guides triage across performance issues, ensuring you collect an audit trail to verify the root cause and fix.

Does this debugging method require any specific dependencies or test frameworks?▼

No, this debugging method does not require specific dependencies or test frameworks. It applies to software projects, services, and test suites by guiding triage from issue intake through reproduction, logging, and verification.

How do I verify a software fix and prove the root cause is resolved?▼

To verify a software fix, re-run the exact reproduction steps and test suites to confirm the bug is resolved. Documenting these post-fix results proves the root cause is addressed and completes the audit trail.