Diagnose and fix bugs using a five-step observe, hypothesize, test, conclude, verify protocol.
npx skills add https://github.com/thienty1207/rust-skills --skill debugging-thienty1207
Please help me install this Agent Skill. Skill: debugging Source: https://github.com/thienty1207/rust-skills/tree/main/debugging Command: npx skills add https://github.com/thienty1207/rust-skills --skill debugging-thienty1207
Systematic debugging framework — structured root-cause analysis, hypothesis-driven debugging, evidence collection, defense-in-depth validation, regression prevention. Use when fixing bugs, investigating failures, diagnosing performance issues, or troubleshooting production incidents.
Describe a reproducible bug scenario and apply the 5-step debugging protocol to identify the root cause.
High-intent search queries and answers about installing and using this skill.
A structured debugging framework systematically isolates software bugs by enforcing an observe, hypothesize, test, conclude, and verify loop to pinpoint exact root causes rather than patching symptoms. It relies on evidence collection across local, staging, and production environments.
Diagnose a production incident using hypothesis-driven debugging by reproducing the failure, forming hypotheses based on observed evidence, testing them systematically, and verifying the fix prevents regressions. This structured approach isolates fault origins across environments.
Use git-bisect for troubleshooting regressions when you need to identify the exact commit that introduced a bug across a range of code changes. It accelerates root-cause tracing by binary searching through commit history to isolate the failure origin.
Yes, defense-in-depth validation works across unit, integration, and end-to-end tests to ensure regression-free fixes. It enforces multi-layer validation after concluding the root cause, verifying that the software bug fix holds across all testing environments.
The best way to troubleshoot performance issues is applying a five-step debugging protocol: observe symptoms, hypothesize causes, test assumptions, conclude the root cause, and verify the resolution. This ensures evidence-based diagnosis across staging and production environments.
Fixing a bug often causes new regressions when the root-cause analysis skips the verification step. Without defense-in-depth validation across unit, integration, and end-to-end tests, isolated fixes fail to account for multi-layered system interactions in production.
oxieDiagnose software errors, isolate root causes, and document fixes.
SteveBronderPlan, implement, test, and summarize tasks autonomously end-to-end.
robit-manAutomate git bisect to identify the commit that introduced a regression.
bugrabilgeDiagnose production outages through log analysis and distributed tracing.
