claudegoodies
Skill

doctor

From asgeirtj

Health-check the user's Claude Code setup and fix issues: diagnose installation health — what the `claude doctor` terminal diagnostics cover — from local data (duplicate or leftover installs, PATH, unparseable settings files, broken or colliding agent definitions); find unused skills, MCP servers, and plugins versus their context cost and disable dead weight; deduplicate local CLAUDE.md files against checked-in ones; trim checked-in CLAUDE.md files by cutting content a session could derive from the codebase (directory layouts, tech-stack lists, architecture overviews) while keeping gotchas, rationale, and non-standard conventions; migrate always-loaded CLAUDE.md guidance into lazy skills and nested CLAUDE.md files; flag slow hooks and context-heavy extensions; check the installed version is current; make auto mode the default permission mode; and pre-approve frequently denied read-only commands. Use when the user asks for a doctor run, checkup, audit, tune-up, or cleanup of their Claude Code setup or configuration.

Audits Claude Code installation, extensions, and CLAUDE.md files, then proposes fixes for user confirmation.

Use it when

  • Running a checkup/audit/tune-up of Claude Code config
  • Finding unused skills, MCP servers, or plugins wasting context
  • Trimming or deduplicating CLAUDE.md files against checked-in versions
  • Checking for stale installs, PATH issues, or slow hooks

Skip it if

  • You don't want it editing settings.json, CLAUDE.md, or permission rules
  • You'd rather review 'claude doctor' output manually yourself
  • You're not comfortable granting auto-mode default permissions it may propose

Facts

Repository
asgeirtj/system_prompts_leaks
Status
Actively maintained
Last commit
Source file
Anthropic/Claude Code/bundled-skills/doctor/SKILL.md

Source preview

The instructions Claude Code reads when this skill runs.

# Claude Code Doctor

Health-check my Claude Code setup and fix what's wrong: diagnose installation health (what the `claude doctor` terminal diagnostics cover), find extensions that cost context but never get used, deduplicate my LOCAL memory files against checked-in ones, trim checked-in CLAUDE.md files down to what a session can't derive on its own, migrate the always-loaded guidance that survives to lazy loading, flag slow hooks, verify my installed version is current, make auto mode my default permission mode, and pre-approve the read-only commands I keep getting denied on.

## Ground rules

- **Propose, then confirm, then apply — and recommend, don't just offer.** Run every check read-only first and present the full report. Then confirm in at most TWO questions — never a question per check and never a long multi-select over every group. (1) ONE consolidated cleanup AskUserQuestion covering checks 0-4 and 7: options are "Clean up everything (recommended)" first, "Let me pick" second, "No, keep everything" last; only if the user picks "Let me pick", ask one follow-up multiSelect question with an option per action group (split it only if there are more than 4 groups — AskUserQuestion caps options at 4). (2) A SEPARATE permission question for checks 8 and 9, never folded into the cleanup bundle: those change what runs without asking, and a user consenting to decluttering must
View full source on GitHub →

Other skills