Debug Code Systematically
Transforms debugging into systematic problem-solving via reproduction, hypothesis testing, binary search, and documented verification.
Why it matters
Transform debugging from frustrating guesswork into systematic problem-solving. This skill provides proven strategies, powerful tools, and methodical approaches to track down elusive bugs and investigate performance issues.
Outcomes
What it gets done
Reproduce issues and capture logs, traces, and environment details.
Form hypotheses and design controlled experiments.
Narrow scope with binary search and targeted instrumentation.
Document findings and verify fixes.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-debugging-strategies | bash Overview
Debugging Strategies
A debugging strategies skill using systematic reproduction, hypothesis testing, and binary search to narrow down and verify fixes. Use for tracking down elusive bugs, performance issues, production incidents, or distributed systems debugging; not for non-reproducible issues or feature development.
What it does
This skill transforms debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
Its approach: reproduce the issue and capture logs, traces, and environment details; form hypotheses and design controlled experiments; narrow scope with binary search and targeted instrumentation; and document findings and verify the fix. It references a bundled resources/implementation-playbook.md for detailed debugging patterns and checklists.
When to use - and when NOT to
Use this skill when tracking down elusive bugs, investigating performance issues, debugging production incidents, analyzing crash dumps or stack traces, or debugging distributed systems.
Not when there is no reproducible issue or observable symptom, for purely feature development tasks, or when logs/traces/runtime signals cannot be accessed.
Inputs and outputs
Inputs: a bug, performance issue, production incident, crash dump, or distributed-systems failure with some observable symptom.
Outputs: a reproduced issue with captured logs/traces/environment details, tested hypotheses narrowed via binary search and instrumentation, documented findings, and a verified fix.
Integrations
A bundled resources/implementation-playbook.md for detailed debugging patterns and checklists.
Who it's for
Developers debugging elusive bugs, performance issues, production incidents, or distributed systems who want a systematic, hypothesis-driven investigation process.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.