rune-debug

Diagnose root causes of bugs through structured hypothesis testing and evidence tracing.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-debug-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-debug
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-debug
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-debug-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging often devolves into guesswork, random code changes, and endless re-reading of the same files. This Skill enforces a disciplined root-cause investigation workflow that reproduces errors, gathers evidence, tests hypotheses systematically, and hands off a precise diagnosis — without ever touching the code itself. ## Core Features & Use Cases - Structured Hypothesis Testing: Forms exactly 2-3 ranked hypotheses, tests each with file:line evidence, and marks them CONFIRMED or RULED OUT, with a hard limit of 3 cycles before escalation. - Known Error Pattern Matching: Matches errors against a built-in catalog (MODULE_NOT_FOUND, ASYNC_DEADLOCK, PATH_MISMATCH, etc.) to skip hypothesis cycling for recognized patterns. - Scope Lock & Anti-Loop Guards: Locks investigation to the narrowest affected directory and detects evidence re-gathering loops to prevent analysis paralysis. - Use Case: A test fails with an unclear stack trace deep in execution. The Skill reproduces the error, backward-traces the invalid data to its origin, identifies the exact file:line root cause, and emits a Debug Report handed off to the fix skill. ## Quick Start Ask the agent to debug the failing test or error message you are seeing and produce a root cause report without changing any code.

Frequently Asked Questions about rune-debug

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

FAQPage Schema
How do I debug a failing test with an unclear error?

Reproduce the error first, then gather evidence by reading the stack trace files and searching for the error string. Form 2-3 specific hypotheses ordered by likelihood, test each with targeted reads or single test runs, and mark each CONFIRMED or RULED OUT with file:line evidence.

What is root cause analysis for software bugs?

Root cause analysis traces an error backward from where it crashes to where the invalid data originates. The Skill enforces this by requiring evidence gathering before hypothesizing and prohibiting fixes at the crash site rather than the source.

Why does debugging keep re-reading the same files without progress?

This is an evidence re-gathering loop, a common stuck pattern. The Skill detects it via hash-based loop detection: reading the same file:line twice or running the same failing test three times triggers a forced hypothesis or handoff with the current diagnosis.

Can this Skill fix the bug after finding the root cause?

No. Debug investigates only and never modifies code, enforced by a hard gate. After identifying the root cause, it emits a structured Debug Report and hands off to the rune-fix skill with the diagnosis and fix direction.

What happens when the same bug keeps coming back after fixes?

After three failed fix attempts, the 3-Fix Escalation Rule triggers: same-category blockers escalate to brainstorm for a different approach, while different bugs each time indicate architectural problems requiring module redesign via the plan skill.