skills.rest
gannonh
gannonhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug-like-expert

Diagnose complex software issues through evidence gathering and hypothesis testing.

58|6|Updated Feb 26, 2026
Search Tags:#code analysis#debugging#troubleshooting#root cause analysis#verification#hypothesis testing
One-click install
npx skills add https://github.com/gannonh/kata --skill debug-like-expert-gannonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-like-expert
Source: https://github.com/gannonh/kata/tree/main/apps/cli/src/resources/skills/debug-like-expert
Command: npx skills add https://github.com/gannonh/kata --skill debug-like-expert-gannonh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, scientific approach to debugging complex software issues that resist standard troubleshooting methods, ensuring root causes are identified and verified.

Core Features & Use Cases

  • Methodical Investigation: Employs evidence gathering, hypothesis testing, and rigorous verification.
  • Cognitive Bias Mitigation: Encourages skepticism towards one's own code to overcome blind spots.
  • Read-Only Analysis: Focuses solely on diagnosis without making code modifications during the investigation phase.
  • Use Case: When a critical production bug appears that cannot be easily reproduced or fixed with conventional methods, this Skill activates a systematic, scientific debugging protocol to uncover the underlying issue.

Quick Start

Use the debug-like-expert skill to investigate the intermittent API failure reported in the staging environment.

Frequently Asked Questions about debug-like-expert

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

FAQPage Schema
How do I find the root cause of an intermittent software bug that resists standard troubleshooting?▼

Root cause analysis for intermittent bugs requires a methodical investigation protocol, gathering evidence and testing hypotheses scientifically to overcome cognitive biases and verify the actual source.

What is the best way to debug complex code failures when I cannot easily reproduce the issue?▼

Debugging complex, non-reproducible failures demands a rigorous, read-only analysis approach that emphasizes skepticism towards self-authored code to identify blind spots and systematically validate the root cause.

Can I use systematic hypothesis testing for diagnosing critical production bugs?▼

Hypothesis testing is highly effective for critical production bugs, providing a scientific method framework to rigorously verify suspected issues without making premature code modifications during the investigation phase.

Why does my standard troubleshooting approach keep failing to identify the underlying software issue?▼

Standard troubleshooting often fails when cognitive bias obscures self-authored code flaws, requiring a shift to methodical evidence gathering and rigorous verification to systematically uncover the true root cause.

When do I need a scientific method approach for code analysis?▼

A scientific method approach for code analysis is needed when conventional troubleshooting fails, demanding rigorous verification and evidence gathering to systematically identify and validate complex software root causes.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
haJ1thaJ1t

systematic-debugging

Diagnose bugs to verified root cause using reproduce-minimize-hypothesize-bisect-confirm.

Community
Advanced
acartineacartine
1

investigate

Trace runtime failures with file:line citations before proposing fixes.

Community
Advanced
MissTullyMissTully

canary

Monitor live apps via periodic screenshots and baseline comparisons.

Community
Advanced