Diagnose bugs via a four-phase root-cause investigation workflow.
npx skills add https://github.com/lukebaze/forex-rebate-bot --skill debugging-lukebaze
Please help me install this Agent Skill. Skill: Debugging Source: https://github.com/lukebaze/forex-rebate-bot/tree/main/.opencode/skill/debugging Command: npx skills add https://github.com/lukebaze/forex-rebate-bot --skill debugging-lukebaze
Debugging can be time-consuming and error-prone when issues span multiple components; this Skill provides a disciplined, four-phase framework to identify root causes before fixes, reducing wasted effort and preventing symptom-focused interventions.
Use Cases: Resolve test failures, unexpected behavior, performance issues, or integration problems by following the methodical process.
Begin by reproducing the issue, gathering evidence across components, and applying Phase 1 root-cause investigation before attempting fixes.
High-intent search queries and answers about installing and using this skill.
Systematic debugging is a structured investigation workflow that traces data backward through call stacks to locate the original trigger. It enforces root-cause analysis before fixes, preventing symptom-focused interventions across multi-component systems.
Debug test failures and regressions by following a four-phase framework: root cause investigation, pattern analysis, hypothesis testing, and implementation. Begin by reproducing the issue and gathering evidence across components before attempting any fixes.
The best way to trace a root cause is applying Phase 1 root-cause investigation, which traces data backward through call stacks to locate the original trigger. This uses instrumentation guidelines to gather evidence before forming hypotheses.
Yes, defense-in-depth validation applies to performance issues and unexpected behavior by validating data at entry, business logic, environment guards, and debug instrumentation. This makes bugs structurally unlikely across multi-component systems.
Verify a bug fix by running fresh verification steps in Phase 4 to confirm outcomes before completion. This ensures the root-cause fix resolves the original issue without introducing regressions across the system.
Avoid using a systematic debugging framework for trivial, single-component issues where the root cause is immediately obvious. The four-phase investigation process is designed for complex bugs spanning multiple components where symptom-focused fixes risk wasted effort.
KodingDevIdentify and resolve root causes of bugs and test failures.
Dmccarty30Investigate root causes through four-phase debugging before implementing fixes.
krzemienskiEnforce five-layer data validation across API boundaries and processing checkpoints.
jacardlDiagnose bugs through structured root-cause investigation with evidence gathering and hypothesis testing.
