Debug

作者 anthropicsae1513ea94dc無授權條款27K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

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.

精選僅含說明Software Development

AI 產生的概覽

執行結構化除錯流程，重現、隔離、診斷並修復軟體問題。

功能: 引導代理依四個步驟除錯：重現問題、隔離受影響的元件或程式碼路徑、診斷根本原因並提出修正方案。它會產出一份 Markdown 除錯報告，包含重現資訊、根本原因、修正方案與預防措施。在可用時，它也可以選用已連線的監控、原始碼控管或專案追蹤工具。
適用情境: 適用於收到錯誤訊息或堆疊追蹤、行為在預備環境與正式環境等不同環境間不一致，或部署後出現問題且原因不明顯的情況。
執行需求: 不隨附指令碼，僅為指示。只需提供問題描述即可使用；選用的已連線監控、原始碼控管或專案追蹤工具可補充記錄、近期變更與相關工單。

/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.

來源與署名

來源：anthropics/knowledge-work-plugins位於engineering/skills/debug提交ae1513e

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 anthropics/knowledge-work-plugins 的技能

Ticket Deflector

anthropics

精選

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."

待分類27K今天更新

Tax Season Organizer

anthropics

精選

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."

待分類27K今天更新

Tax Prep

anthropics

精選

根據已結帳的帳目準備稅務資料：季度預估繳稅明細，或年終 1099-NEC 清單與會計師資料包。

Business & Finance27K今天更新

Smb Onboard

anthropics

精選

引導小型企業主完成首次設定：連接工具、執行一次展現價值的配方、記錄業務背景並設定每週檢查節奏。

Productivity & Workflow27K今天更新

Smb Router

anthropics

精選

將小型企業主的需求轉接到合適的外掛技能或指令，並說明可用功能。

Productivity & Workflow27K今天更新

Month End Prep

anthropics

精選

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."

待分類27K今天更新

Debug

/debug

Usage

How It Works

What I Need From You

Output

If Connectors Available

Tips

來源與署名

更多來自 anthropics/knowledge-work-plugins 的技能

Ticket Deflector

Tax Season Organizer

Tax Prep

Smb Onboard

Smb Router

Month End Prep

更多Software Development技能

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices