debugging-with-tools
Use for investigation-heavy work. Prefer tool-driven evidence (search, logs, diffs) before changing code.
When & Why to Use This Skill
This Claude skill streamlines complex software debugging by prioritizing evidence-based investigation over guesswork. It enables developers to systematically identify root causes by leveraging search tools, log analysis, and control flow tracing, ensuring high-precision code fixes and minimizing the risk of regressions in large codebases.
Use Cases
- Root Cause Analysis: Systematically searching the codebase for specific error strings or symbols to locate the source of a failure.
- Regression Investigation: Using git diff and status tools to analyze recent changes and determine which commit introduced a bug.
- Control Flow Tracing: Mapping the execution path from entry points to side effects to understand how data moves through complex systems.
- Environment Troubleshooting: Inspecting configuration files and environment assumptions to resolve deployment-specific or infrastructure-related issues.
- Iterative Bug Fixing: Implementing focused, one-at-a-time code changes followed by immediate verification to ensure stable resolutions.
| name | debugging-with-tools |
|---|---|
| description | Use for investigation-heavy work. Prefer tool-driven evidence (search, logs, diffs) before changing code. |
Workflow
- Confirm the symptom and collect a single source of truth (error output/log).
- Search the codebase for the error string / endpoint / symbol.
- Trace control flow (entrypoint → callers → side effects).
- Inspect configuration and environment assumptions.
- Make one change at a time and re-check the symptom.
Tooling checklist
rgfor string/symbol searchgit diff/git statusfor change review- Minimal, focused test/run commands