skills.rest
idehen-divine
idehen-divineCOMMUNITY
Explore all skills by this author →
Website𝕏@idehen_divineGitHub

debug

Diagnose and fix root causes of bugs through a structured reproduce and verify loop.

Updated Sep 19, 2026
Search Tags:#debugging#troubleshooting#bug fix#root cause analysis#git bisect#test failure#regression test
One-click install
npx skills add https://github.com/idehen-divine/lumished --skill debug-idehen-divine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/idehen-divine/lumished/tree/main/.ai/skills/debug
Command: npx skills add https://github.com/idehen-divine/lumished --skill debug-idehen-divine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a test fails for a non-obvious reason or behavior is unexpected, guessing at fixes wastes time and often patches symptoms while the real bug survives. This Skill runs a disciplined root cause investigation so the actual cause is proven by evidence before any code changes. ## Core Features & Use Cases - Structured investigation loop: Reproduce the bug deterministically, localize it by bisecting code paths or git history, then test one falsifiable hypothesis at a time until the cause is confirmed. - Minimal root cause fixes: Applies the smallest targeted change that addresses the proven cause, with no opportunistic refactors or scope creep. - Regression protection: Verifies the fix against the original reproduction and surrounding test suite, adds a regression test, and greps for sibling occurrences of the same root cause. - Use Case: A CI test fails intermittently with a timezone-related error. The Skill captures the symptom, makes the failure deterministic, bisects to the date parsing code, proves the cutoff is off by the timezone offset, fixes the parsing, and adds a regression test. ## Quick Start Run the debug skill to find and fix the root cause of this failing test, then add a regression test.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a failing test?▼

Reproduce the failure deterministically, then localize it by bisecting the code path or git history. State one falsifiable hypothesis, test it with the smallest experiment, and only fix after the cause is confirmed by evidence.

How to debug intermittent or flaky test failures?▼

First make the failure deterministic by controlling timing, ordering, data, or concurrency factors. A bug you cannot reproduce on command cannot be proven fixed, so add instrumentation to catch it rather than fixing blind.

Can this debugging workflow run in a subagent?▼

Yes, for non-trivial investigations you can spawn a subagent with Read, Bash, Grep, Glob, Edit, and Write tools. Set the model explicitly and require it to report the root cause with evidence, not just a fix claim.

Why should I avoid fixing a bug before proving the cause?▼

An unverified fix often patches the symptom, like clamping a null value, while the underlying cause survives. Testing one hypothesis at a time ensures every change produces a meaningful result and the fix addresses the real problem.

When should a bug be escalated to architecture review instead of patched?▼

When investigation reveals the cause is a flawed design decision rather than a coding mistake, the right fix may be a spec update. The Skill flags this case and points to an architecture review rather than papering over it.

Related Skills

Explore More Software Engineering Skills→
codeaholicguycodeaholicguy
1.6k

structured-debug

Diagnose bugs through evidence-based reproduction, hypothesis testing, and validated fix plans.

Community
Intermediate
unclehowellunclehowell

test-driven-development

Enforce a test-first workflow requiring failing tests before production code.

Community
Intermediate
nhouseholdernhouseholder

root-cause-reflection

Identify flawed assumptions and reasoning gaps after significant bug fixes.

Community
Advanced
withmartian-sandboxwithmartian-sandbox

condition-based-waiting

Replace arbitrary timeouts with configurable condition-based polling in test suites.

Official
Intermediate