Run /doctor and /insights
Two commands that most people never type, and both are cheap to run.
/doctor
Section titled “/doctor”/doctor/doctor (alias /checkup, Claude Code v2.1.206 or later) is a health check for your setup. It:
- Reports skills, MCP servers, and plugins you are not using, alongside what they cost in context.
- Trims checked-in
CLAUDE.mdfiles by cutting content Claude could derive from the codebase. - Migrates always-loaded guidance that remains into skills and nested
CLAUDE.mdfiles that load on demand.
You can steer it:
/doctor propose trims to my CLAUDE.md that will not change behaviorReview the suggestions before accepting them. The goal is a shorter always-loaded file, with task-specific material moved to skills where it loads only when needed.
/insights
Section titled “/insights”/insights/insights analyzes your recent sessions on this machine and writes an HTML report: what you work on, friction points such as misunderstood requests or buggy code, and suggestions for using Claude Code more effectively.
A single run covers up to 200 sessions it has not seen before.
It only works on sessions that still exist locally. If you keep the default 30-day cleanupPeriodDays, the report has less to work with.
When to run them
Section titled “When to run them”/doctor: after adding MCP servers or plugins, or when/contextshows startup content you do not recognize./insights: every few weeks, to spot patterns you would not notice session by session.