# /doctor Command

> It checks your setup and offers to fix what is wrong.

**Field:** Artificial Intelligence  
**Category:** Claude Code  
**Also known as:** /doctor, /checkup, Claude Code setup checkup

## Think of it like

It is like a checkup at the doctor. They look you over, then tell you what to fix.

## Definition

/doctor is a bundled skill that runs a checkup on your Claude Code setup. It looks at the install, the settings files, your extensions and your CLAUDE.md. It flags things like a broken settings file, an extension you never use, or CLAUDE.md lines Claude could learn from the code. Then it proposes fixes and applies them only after you agree. If Claude Code will not start at all, run claude doctor in your shell instead.

## Example

Jack's hooks stopped running. /doctor finds that one settings file is broken, shows the bad line, and fixes it once he says yes.

## Example code

```console
/doctor
```

Run a checkup on your Claude Code setup.

## Why it matters

When something does not load, you get a list of causes. You do not spend the day guessing.

## Common mistake

Using it for a bug that shows up mid-task. /doctor checks the setup. /debug reads the log of what happens while a session runs.

## Three principles

- **Checks the setup.** Install, settings, extensions.
- **Proposes fixes.** You say yes first.
- **Or from the shell.** claude doctor.

## Related terms

- [claude doctor Command](https://learn.benibix.com/term/ai/claude-doctor-command)
- [/debug Command](https://learn.benibix.com/term/ai/debug-command)
- [CLAUDE.md](https://learn.benibix.com/term/ai/claude-md)
- [/config Command](https://learn.benibix.com/term/ai/config-command)

## Told apart from

- [/doctor vs /debug](https://learn.benibix.com/compare/doctor-command-vs-debug-command): People often think /doctor and /debug both just find what is wrong. They look in different places. /doctor checks your setup: the install, the settings files, your extensions and CLAUDE.md. It proposes fixes and applies them after you agree. /debug turns on the log of a running session and reads it, to find a problem that shows up while you work. Run /doctor when something will not load, and /debug when something goes wrong mid-task.
- [claude doctor vs /doctor](https://learn.benibix.com/compare/claude-doctor-command-vs-doctor-command): People think claude doctor and /doctor are the same check typed in two places, and they are not. claude doctor runs in your shell with no session open. It only reads, so it is the one to use when Claude Code will not start. /doctor runs inside a session. It checks more, and it offers to fix what it finds once you say yes.

## Taught in

- [Install, Update and Doctor](https://learn.benibix.com/learn/ai-claude-code-commands/install-update-and-doctor): Claude Code Commands, 2/17

![The checkup looks at the install, the settings files, the extensions and CLAUDE.md. It proposes fixes, and applies them only after you say yes.](https://learn.benibix.com/diagrams/cmd-doctor.svg)

---

Source: https://learn.benibix.com/term/ai/doctor-command
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
