Guide engineers through a four-phase evidence-driven debugging workflow for flaky failures.
npx skills add https://github.com/cjennings/rulesets --skill debug-cjennings
Please help me install this Agent Skill. Skill: debug Source: https://github.com/cjennings/rulesets/tree/main/debug Command: npx skills add https://github.com/cjennings/rulesets --skill debug-cjennings
Investigate a bug or test failure methodically through four phases — understand the symptom, isolate variables, form and test hypotheses, then fix at the root. The workflow emphasizes collecting evidence before proposing fixes, rejects shotgun debugging, and escalates to architectural investigation after three failed fix attempts.
Describe the symptom and then work through Phase 1 to Phase 4 in order to gather evidence and identify the root cause before proposing a fix.
High-intent search queries and answers about installing and using this skill.
To debug flaky test failures with inconsistent logs, follow a structured, evidence-driven workflow that enforces four sequential phases: understand the symptom, identify the root cause, verify the hypothesis with failing tests, and fix with minimal changes.
The best way to find the root cause of intermittent production bugs is applying a phase-ordered debugging workflow that captures reproduction steps, logs, and traces as evidence to validate root-cause hypotheses before implementing fixes.
To stop shotgun debugging when fixing software failures, use an evidence-centric analysis process that requires explicit root-cause hypotheses and validation through failing tests, rejecting ad-hoc fixes to ensure traceability.
You should escalate an incident during root-cause analysis after three failed fix attempts, triggering an architectural investigation to resolve the stagnation and document remaining evidence.
Yes, this debugging workflow supports cross-checking insights by aligning with companion practices like start-work, root-cause-trace, and five-whys analysis methodologies.
To systematically debug unclear software failures, describe the symptom, then work through Phase 1 to Phase 4 in order: understand the symptom, identify the root cause, verify hypotheses with evidence, and implement a minimal, well-documented fix.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
lumenhelixsolutionsIdentify software bug root causes and implement test-first verified fixes.
StudentCristianGuide multi-branch Five Whys analysis with evidence validation and preventive solutions.
csuzngjhAppends user-provided rule arguments to the Ad-hoc Rules section of USER_CONTEXT.md.
