backend-debug

Installation
SKILL.md

Backend Debug

Fix the bug that was reported, prove it is fixed, and write down why it happened. Nothing else changes in the same run.

When to Use

  • A request returns 500, an exception or stack trace appears, or output is wrong.
  • A test fails, a test is flaky, or behavior regressed after a change.
  • The user asks "why does X happen?" or "why is X slow?".
  • A production incident needs a root cause (read-only triage first; see Step 2).

Not for:

  • New behavior the code never had: backend-implement. If the "bug" turns out to be a missing feature, say so and hand off.
  • Restructuring without behavior change: backend-refactor, in a separate change set after the fix.
  • Writing or applying migrations: backend-migrate (see Handoffs).
  • A security review or audit: backend-security. A vulnerability found while debugging is logged and handed off there.

Before You Start

Installs
1
GitHub Stars
17
First Seen
7 days ago