debug-like-expert

Execute a structured debugging workflow for evidence-based root-cause analysis.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/mrjuguy/kitchen_assistant --skill debug-like-expert-mrjuguy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-like-expert
Source: https://github.com/mrjuguy/kitchen_assistant/tree/main/.agent/skills/debug-like-expert
Command: npx skills add https://github.com/mrjuguy/kitchen_assistant --skill debug-like-expert-mrjuguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep analysis debugging mode activates a disciplined investigation protocol with evidence gathering, hypothesis testing, and rigorous verification when standard troubleshooting fails.

Core Features & Use Cases

  • Evidence-based diagnosis templates and checklists
  • Automated domain-expertise loading and optional guidance
  • Structured root-cause analysis workflow with explicit verification steps

Quick Start

Execute the methodical debugging workflow to systematically identify root causes and verify fixes.

Frequently Asked Questions about debug-like-expert

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

FAQPage Schema
What is methodical debugging and when should I use it for complex issues?

Methodical debugging is an evidence-based investigation workflow used when standard troubleshooting fails. It enforces hypothesis testing and rigorous verification to identify root causes in multi-file codebases with complex failure modes where quick fixes do not work.

How do I debug a complex issue across a multi-file codebase when quick fixes fail?

To debug a complex issue, execute a structured root-cause analysis workflow that gathers evidence, tests hypotheses, and applies explicit verification steps. This methodical approach ensures thorough verification and prevents recurring failures in multi-file codebases.

Can I load specific domain expertise to help investigate a tough software bug?

Yes, the debugging workflow supports automated domain-expertise loading and optional guidance. This provides specialized context during evidence-based diagnosis, helping you systematically identify root causes in complex or unfamiliar codebases.

What is the best way to verify a root-cause analysis before applying a code fix?

The best way to verify root-cause analysis is through explicit verification steps enforced by a structured debugging workflow. This methodical approach requires evidence-based diagnosis templates and skepticism toward your own code to confirm the identified root cause before resolution.

Does evidence-based debugging work for complex failure modes where standard troubleshooting fails?

Yes, evidence-based debugging is specifically designed for complex failure modes where standard troubleshooting fails. It activates a disciplined investigation protocol with evidence gathering, hypothesis testing, and rigorous verification to identify root causes in multi-file codebases.