doctor
Skill1 starsChanged 7 months agoApache-2.0View on GitHub
Self-heals this project's Claude Code setup. Diagnoses broken or missing pieces — skills with no SKILL.md, hooks referenced but absent or non-executable, invalid settings.json, bloated CLAUDE.md — scores health, and applies safe fixes. Use when something in the setup seems off, after edits to .claude/, when a hook or skill isn't firing, or on a `[heal]` nudge. Triggers: 'is my setup ok', 'fix my claude setup', 'why isn't my skill/hook working', '/doctor'.
85 other projects use a version of this.
Adopted by
Most recently taken up by
- aaroncohn/babysittertheir own version, first seen Nov 16, 2026
- Yomudogly/oh-my-agytheir own version, first seen Nov 16, 2026
- timursafiullin/aodtheir own version, first seen Nov 15, 2026
- mkritter3/codex-paired-superpowerstheir own version, first seen Nov 15, 2026
- dcamunas/model-routertheir own version, first seen Nov 15, 2026
- Noah-OS/longhaultheir own version, first seen Nov 15, 2026
Used with
Projects with it also use uninstall, cancel and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkilluninstall
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.
Also in 6 projects that use this
woosikkimSkillcancel
Clear any stale OMC-Slim state
Also in 3 projects that use this
ibahgatSkillmode
Inspect or switch omi operating mode/profile for speed, depth, autonomy, or strict quality gates.
Also in 3 projects that use this
BlockSkillopen
Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.
Also in 3 projects that use this
QinghongLinSkilleditor
Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).
Also in 3 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 15 projects that use this
Other versions85 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 85
- Yeachan-Heo/oh-my-codex★ 34ksame name
- jihe520/MathModelAgent★ 6.2ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
- fakechris/obsidian_vault_pipeline★ 165same name
- NoobyGains/godmode★ 120same name
- Rich627/whatsapp-claude-plugin★ 114same name
- bluzir/claude-code-design★ 102same name
- jjanczur/tyran★ 79same name
- svy04/ballast★ 73same name
- Hainrixz/agente-pagokit★ 68same name
75 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyze-repoSkill
- augmentSkill
- code-reviewSkill
- context-guardSkill
- dep-checkSkill
- forgeSkill
- git-workflowSkill
- learnSkill
- onboardingSkill
- security-scanSkill
- self-updateSkill
- test-runnerSkill
- tipsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 64 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Keep the setup healthy without the user having to understand its internals.
- Distinctive: line 54
If a finding's root cause is ambiguous, show the user the finding and the proposed fix before applying it.
“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Purpose
Keep the setup healthy without the user having to understand its internals. The diagnosis is fully deterministic (no guessing); repairs are explicit and safe.
When to use this
- A hook/skill/command isn't behaving, or the user edited
.claude/by hand. - A
[heal]nudge appeared (a tool failed repeatedly — see.claude/state/failures.jsonl). - Proactively after
augment/forgewrites new config.
Steps
1. Diagnose
python3 .claude/engine/doctor.py --jsonReturns {score, errors, warnings, findings[]}. Each finding has where, problem,
fix, and auto_fixable.
2. Apply the safe auto-fixes
python3 .claude/engine/doctor.py --applyThis performs only non-destructive repairs (e.g. chmod +x hooks). Everything else
is left to you with a precise fix string.
3. Repair the rest, in order of severity
- error first (a missing hook reference, a skill with no SKILL.md, invalid JSON).
Fix the root cause: restore/author the file, correct the JSON, or remove the dead
reference. For a skill dir missing SKILL.md, use
forge(or delete it if obsolete). - warn next (non-executable hook already covered by --apply; oversized CLAUDE.md → trim and move detail into skills; agent missing frontmatter → add it).
- info as time allows.
4. Re-check and learn
Re-run the diagnosis until errors: 0. If a failure pattern recurs, record it so the
setup avoids it next time:
echo '{"category":"fix","text":"<what was broken> → <how fixed>","tags":["heal"]}' \
| python3 .claude/engine/learn.py addOutput
A health score and a clean before/after: what was broken, what was auto-fixed, what you repaired, ending at 0 errors.
Guardrails
- Auto-fix is safe-only; never delete user content to "fix" a finding without asking.
- If a finding's root cause is ambiguous, show the user the finding and the proposed fix before applying it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

