Debug

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

FeaturedInstructions onlySoftware Development

AI-generated overview

Runs a structured debugging session to reproduce, isolate, diagnose, and fix a software issue.

What it does: Guides an agent through a four-step debugging workflow: reproduce the problem, isolate the affected component or code path, diagnose the root cause, and propose a fix. It produces a markdown debug report covering reproduction details, root cause, fix, and prevention steps. It may optionally use connected monitoring, source control, or project tracker tools when available.
When to use it: Use it when given an error message or stack trace, when behavior differs between environments such as staging and production, or when something broke after a deploy and the cause is not obvious.
Requirements: No scripts ship with it; it is instructions only. It works with just the problem description, though optional connected monitoring, source control, or project tracker tools can add logs, recent changes, and related tickets.

/debug

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Run a structured debugging session to find and fix issues systematically.

Usage

How It Works

┌─────────────────────────────────────────────────────────────────┐│                       DEBUG                                        │├─────────────────────────────────────────────────────────────────┤│  Step 1: REPRODUCE                                                ││  ✓ Understand the expected vs. actual behavior                   ││  ✓ Identify exact reproduction steps                             ││  ✓ Determine scope (when did it start? who is affected?)        ││                                                                    ││  Step 2: ISOLATE                                                   ││  ✓ Narrow down the component, service, or code path             ││  ✓ Check recent changes (deploys, config changes, dependencies) ││  ✓ Review logs and error messages                                ││                                                                    ││  Step 3: DIAGNOSE                                                  ││  ✓ Form hypotheses and test them                                 ││  ✓ Trace the code path                                           ││  ✓ Identify root cause (not just symptoms)                      ││                                                                    ││  Step 4: FIX                                                       ││  ✓ Propose a fix with explanation                                ││  ✓ Consider side effects and edge cases                          ││  ✓ Suggest tests to prevent regression                           │└─────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐│                       DEBUG                                        │├─────────────────────────────────────────────────────────────────┤│  Step 1: REPRODUCE                                                ││  ✓ Understand the expected vs. actual behavior                   ││  ✓ Identify exact reproduction steps                             ││  ✓ Determine scope (when did it start? who is affected?)        ││                                                                    ││  Step 2: ISOLATE                                                   ││  ✓ Narrow down the component, service, or code path             ││  ✓ Check recent changes (deploys, config changes, dependencies) ││  ✓ Review logs and error messages                                ││                                                                    ││  Step 3: DIAGNOSE                                                  ││  ✓ Form hypotheses and test them                                 ││  ✓ Trace the code path                                           ││  ✓ Identify root cause (not just symptoms)                      ││                                                                    ││  Step 4: FIX                                                       ││  ✓ Propose a fix with explanation                                ││  ✓ Consider side effects and edge cases                          ││  ✓ Suggest tests to prevent regression                           │└─────────────────────────────────────────────────────────────────┘

What I Need From You

Tell me about the problem. Any of these help:

Error message or stack trace
Steps to reproduce
What changed recently
Logs or screenshots
Expected vs. actual behavior

Output

markdown

## Debug Report: [Issue Summary]
### Reproduction- **Expected**: [What should happen]- **Actual**: [What happens instead]- **Steps**: [How to reproduce]
### Root Cause[Explanation of why the bug occurs]
### Fix[Code changes or configuration fixes needed]
### Prevention- [Test to add]- [Guard to put in place]

## Debug Report: [Issue Summary]
### Reproduction- **Expected**: [What should happen]- **Actual**: [What happens instead]- **Steps**: [How to reproduce]
### Root Cause[Explanation of why the bug occurs]
### Fix[Code changes or configuration fixes needed]
### Prevention- [Test to add]- [Guard to put in place]

If Connectors Available

If ~~monitoring is connected:

Pull logs, error rates, and metrics around the time of the issue
Show recent deploys and config changes that may correlate

If ~~source control is connected:

Identify recent commits and PRs that touched affected code paths
Check if the issue correlates with a specific change

If ~~project tracker is connected:

Search for related bug reports or known issues
Create a ticket for the fix once identified

Tips

Share error messages exactly — Don't paraphrase. The exact text matters.
Mention what changed — Recent deploys, dependency updates, and config changes are top suspects.
Include context — "This works in staging but not prod" or "Only affects large payloads" narrows things fast.

Source and attribution

Source:anthropics/knowledge-work-pluginsinengineering/skills/debugat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today

Debug

/debug

Usage

How It Works

What I Need From You

Output

If Connectors Available

Tips

Source and attribution

More from anthropics/knowledge-work-plugins

Ticket Deflector

Tax Season Organizer

Tax Prep

Smb Onboard

Smb Router

Month End Prep

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices