grilldebug

Diagnose bugs through one-question-at-a-time interrogation and systematic root cause analysis.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/wesbragagt/nixos-config --skill grilldebug-wesbragagt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilldebug
Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/grilldebug
Command: npx skills add https://github.com/wesbragagt/nixos-config --skill grilldebug-wesbragagt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stubborn bugs often get patched with guesses that fix symptoms instead of causes. This Skill replaces reactive pattern-matching with a disciplined process: it explores the code first, interviews you one question at a time to narrow the failure tree, then runs a structured root cause analysis before any fix is written. ## Core Features & Use Cases - Code-First Exploration: Reads every file in the stack trace, checks git history, and traces callers before asking you anything, so questions target only what the code cannot answer. - Guided Interrogation: Drives a one-question-at-a-time interview covering reproduction, timeline, scope, frequency, and hypothesis testing until a single best-supported theory remains. - Systematic Diagnosis: Runs four phases — root cause investigation, pattern classification, falsifiable hypothesis testing, and fix recommendation — then reports root cause, evidence, fix, and regression test plan. - Use Case: You have an intermittent production failure that only appears under load. Invoke grilldebug with the error description; it walks you through targeted questions, traces the code, and delivers a committed root cause hypothesis with a concrete fix and test recommendation. ## Quick Start Ask the AI to run grilldebug on your bug, for example: "grilldebug — the checkout API intermittently returns 500 errors under load, help me find the root cause."

Frequently Asked Questions about grilldebug

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

FAQPage Schema
How do I find the root cause of a bug systematically?

Start by reading every file in the stack trace and recent git history, then narrow the failure tree with targeted questions about reproduction, timeline, and scope. Commit to one falsifiable hypothesis and confirm it with evidence before recommending a fix.

How do I debug an intermittent or hard-to-reproduce error?

Focus on what varies between a passing and failing run: inputs, state, load, timing, and environment. Ask what changed before the failures started and probe boundary conditions like concurrency, empty data, or first/last records.

Does grilldebug write the fix for me?

No. It produces a diagnosis only: root cause, supporting evidence, a prose description of the required fix, and a regression test recommendation. You confirm the approach before any code is written.

When should I use structured RCA instead of just reading the error?

Use it when the visible error may be a downstream symptom, when quick guesses have failed, or when the bug is intermittent. Simple obvious typos do not need a full interview-driven investigation.

What information should I provide when starting a debugging session?

Provide what is broken, what you expected, what you observed instead, and any error messages or stack traces. Details about when it started and what changed recently significantly speed up the diagnosis.