skills.rest
tinner-deinno
tinner-deinnoCOMMUNITY
Explore all skills by this author →
GitHub

debug-mantra

Diagnose runtime errors through reproduction, fail-path tracing, and hypothesis testing.

1|Updated May 24, 2026
Search Tags:#debugging#troubleshooting#stack trace#hypothesis testing#incident response#engineering workflow#reproduction
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill debug-mantra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-mantra
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/debug-mantra
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill debug-mantra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted debugging cycles by forcing a disciplined workflow: reproduce the issue, pinpoint the fail path, challenge the hypothesis, and reconcile every experiment against a running breadcrumb ledger.

Core Features & Use Cases

  • Verbatim debugging ritual: Starts each session by reciting the four-step mantra exactly as specified to keep decisions consistent.
  • Four-step investigation order: Ensures debugging follows reproducibility → fail-path tracing → hypothesis falsification → cross-run confirmation before any “fix” is proposed.
  • Trigger-driven activation: Activates on /debug-mantra and proactively when debugging begins via bug reports, failure/throwing logs, or pasted stack traces.

Quick Start

Recite the debug-mantra at the start of your debugging session, then follow the four steps in order before proposing any fix.

Frequently Asked Questions about debug-mantra

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

FAQPage Schema
What is the best way to troubleshoot a bug from a stack trace without wasting time?▼

Debugging a bug from a stack trace requires a disciplined debugging workflow that enforces reliable reproduction, fail-path localization, and hypothesis validation against prior observations before proposing any fix.

How do I reproduce a runtime error before I start fixing it?▼

To reproduce a runtime error, you must first recite a four-step debugging mantra, then follow an ordered gating process that verifies reproducibility and narrows the fail path before testing any hypotheses.

Why does my debugging process fail to find the root cause of failed tests?▼

Debugging fails to find the root cause of failed tests when the root cause is pursued without reliable reproduction, clear fail-path localization, or hypothesis validation against prior observations.

How do I use hypothesis testing to diagnose an incident response?▼

Hypothesis testing during incident response mandates a disproof-first approach, challenging your hypothesis and maintaining an experiment ledger that cross-references every run before confirming any conclusion.

Does this debugging workflow work with bug reports that include logs and environment context?▼

This debugging workflow works directly with bug reports that include logs or environment context, activating proactively when debugging begins via failure logs or pasted stack traces.

When should I not use a structured debugging ritual for troubleshooting?▼

You should not use a structured debugging ritual when you need a quick, ad-hoc fix for a trivial issue, as it mandates verbatim recitation and ordered gating of reproducibility before proposing any solution.

Related Skills

Explore More Software Engineering Skills→
KIM-KYOUNG-OHKIM-KYOUNG-OH

issue-bug-report

Convert error logs and stack traces into structured Markdown bug reports.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
xiaoshuangLixiaoshuangLi
1

debugging

Diagnose software defects through reproduction, hypothesis testing, and verification.

Community
Intermediate
Phife726Phife726

data-analyst

Analyze datasets with SQL, pandas, and statistical methods.

Community
Intermediate