AutoGineer
Generated banner for Debug
Generated logo for Debug

Debug

AnthropicOfficialPublished by Anthropic

  • Skill
  • Workflow
  • Software development
  • Apache-2.0
  • No issues found
Download ZIP

From the author

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.
— the description by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The debug skill provides a rigorous, step-by-step framework for troubleshooting software issues. By guiding the user through reproduction, isolation, diagnosis, and remediation, it ensures that the root cause is identified rather than just the symptoms. It integrates with available connectors to pull relevant logs, source control history, and project tracking data to accelerate the resolution process.

What it does

  • Guides users through a structured four-step debugging process.
  • Helps define expected versus actual behavior to clarify the issue.
  • Analyzes logs, recent code changes, and configuration updates to isolate the root cause.
  • Generates a comprehensive debug report summarizing the findings and proposed fix.
  • Suggests preventative measures such as new tests or guards to avoid future regressions.
  • Leverages connected tools like monitoring, source control, and project trackers for deeper insights.

When to use it

  • When you encounter an error message or stack trace that requires investigation.
  • When behavior diverges from expected outcomes and the cause is not immediately obvious.
  • When an issue appears in one environment (e.g., production) but not another (e.g., staging).
  • After a recent deployment or configuration change that correlates with new system instability.

Advantages

  • Promotes a disciplined, scientific approach to troubleshooting.
  • Reduces time spent on trial-and-error by focusing on isolation.
  • Ensures fixes are verified and accompanied by preventative testing.
  • Provides a clear, documented record of the issue and its resolution.

Usage examples

“/debug NullPointerException in user-service at line 42”
The agent initiates a debugging session, requesting reproduction steps and analyzing relevant logs or recent commits to identify the cause of the null reference.
“/debug The payment gateway works in staging but fails in production”
The agent compares environment configurations and recent deployment logs to isolate the discrepancy causing the production failure.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/debug/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip debug.zip -d .agents/skills

Documentation by Anthropic

/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

/debug $ARGUMENTS

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                           │
└─────────────────────────────────────────────────────────────────┘

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

## 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

  1. Share error messages exactly — Don't paraphrase. The exact text matters.

  2. Mention what changed — Recent deploys, dependency updates, and config changes are top suspects.

  3. Include context — "This works in staging but not prod" or "Only affects large payloads" narrows things fast.

Files

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/knowledge-work-plugins · engineering/skills/debug · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download debug.zip