debug

Enforce an evidence-first debugging process that verifies fixes against original symptoms.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill debug-me2resh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/me2resh/apexyard --skill debug-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents repeated fix-deploy cycles by forcing a disciplined, hypothesis-driven debugging workflow that verifies changes against the original symptom.

Core Features & Use Cases

  • Capture symptoms precisely: Collect the exact URL/endpoint, expected vs observed behavior, a minimal repro recipe, and surface evidence (logs/console/headers) before reasoning.
  • Read the architecture first: Inspect the specific files that handle each layer involved in the failing operation rather than guessing.
  • Evidence-first hypothesis ladder: Generate 3–5 candidate causes with confirm/refute tests, gather evidence in order, then implement only after confirmation.
  • Verify against original evidence: Re-run the same evidence command to prove the fix resolves the symptom and doesn’t introduce a new failure mode.

Quick Start

Invoke /debug and provide a symptom summary including the exact URL or command, expected vs observed results, and the minimal repro steps.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a stalled bug investigation when multiple plausible causes exist?

Debug stalled bug investigations by enforcing an evidence-first debugging process that captures symptoms, maps architecture, forms testable hypotheses, and verifies fixes. Generate 3–5 candidate causes with confirm/refute tests before implementing any changes.

What is the best way to stop repeated fix-deploy cycles for a failing web endpoint?

Stop repeated fix-deploy cycles by adopting a hypothesis-driven debugging workflow that verifies changes against the original symptom. Capture the exact URL, expected versus observed behavior, and minimal repro recipe before reasoning about the root cause.

How do I systematically verify a code fix doesn't introduce a new failure mode?

Verify a code fix by re-running the same original evidence command used to capture the symptom. This proves the fix resolves the observed behavior and confirms it does not introduce a new failure mode in the affected web routing or architecture layers.

When should I read application architecture before attempting a bug fix?

Read application architecture before attempting a bug fix when prior fixes have failed or multiple plausible causes exist. Inspect the specific files handling each layer involved in the failing operation to avoid guess-driven changes and ensure accurate incident triage.

Can I use this structured debugging process for multi-layer desktop applications?

Yes, this structured debugging process applies to multi-layer debugging across both web and desktop contexts. It requires architecture reading and confirm/refute evidence tests before implementing a fix, ensuring thorough incident triage regardless of the application environment.

Why does guess-driven debugging fail to resolve complex routing incidents?

Guess-driven debugging fails because it bypasses evidence gathering and architecture reading, leading to unverified changes. Structured hypothesis testing maps the web routing layers involved and confirms the exact cause before a fix is implemented and validated.