debug
Runs a structured debugging session: reproduce, isolate, diagnose and fix, starting from an error, a stack trace or behaviour that diverges.
- Kind
- Skill
- Works with
- Claude Code
- Source
- Claude knowledge-work plugins @ 2574e29377c7
- Path
- engineering/skills/debug/SKILL.md
- Jobs
- Debugging
- Topics
- Debugging
Credit
- Made by
- anthropics
- Original
- github.com/anthropics/knowledge-work-plugins/blob/2574e29377c…
- License
- Apache-2.0
Listed by Skill Manifest; not made by us.
InstallInstall it from a plugin marketplace.
claude plugin install engineering@knowledge-work-plugins
Install factsScanned 2 Nov 2026
- Adds
- .claude/skills/debug/ (the skill folder)
- 1 file(s) the skill refers to
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- 2574e29377c7
- Licence
- Apache-2.0
- Last activity
- 1 Nov 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- Only the main file is read; other files in the folder are not scanned
# /debug > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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 │ │ │ …