debug-mantra

Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb. Recite the mantra block verbatim at the start of any debugging session, then apply the four steps in order before proposing any fix. Trigger on /debug-mantra and proactively whenever debugging starts — user reports a bug, says something is broken/throwing/failing, asks to debug/diagnose/investigate an issue, or pastes a stack trace or error log.

Try your first task

Establish a reliable bug reproduction

Start a fresh conversation. Replace the highlighted placeholders.

Use the debug-mantra skill to investigate this bug: [describe the symptom and paste the error or logs]. The codebase is at [absolute repository path], and the relevant environment and current reproduction steps are [describe them]. Begin with the required mantra, then establish the fastest reliable reproduction and create an initial breadcrumb ledger. Do not propose a fix before the failure is reproducible and its path has been traced.

Required inputs

Bug symptom and error or log output
Absolute repository path
Environment details
Current reproduction steps and inputs

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

Inside SKILL.md

75 lines

Section content has not been verified for this skill yet.

Full source remains withheld under the current source-display policy. Read the author’s source ↗