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