arch-doctor
Skill11 starsChanged 2 days agoApache-2.0View on GitHub
Diagnoses the AI setup and architecture enforcement on this machine: active hooks, loaded boundary rules, build wrapper, `java` on PATH, which `.claude/` this project was written from and what has been edited since, and whether every docker-compose service is actually running with no foreign container on its ports and no image tag disagreeing with the one the test suite pins. Explicit invocation only.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nerviz-ai/nervizword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- nerviz-ai/nerviz★ 11100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-architectSkill
- arch-adoptSkill
- audit-usageSkill
- cache-architectSkill
- claude-code-architect-designerSkill
- docker-architectSkill
- domain-modelingSkill
- git-publishSkill
- gof-design-patternsSkill
- graphql-api-architectSkill
- harness-lessonsSkill
- http-client-architectSkill
- init-projectSkill
- jobs-architectSkill
- messaging-architectSkill
- nerviz-diagramsSkill
- new-feature-implementSkill
- new-featureSkill
- new-projectSkill
- persistence-architectSkill
- platform-upgradeSkill
- project-bootstrapSkill
- project-configSkill
- report-issueSkill
- rest-api-architectSkill
- search-architectSkill
- security-architectSkill
- sonar-lessonsSkill
- sonarqube-setupSkill
- spikeSkill
- test-architectSkill
- transport-security-setupSkill
- triage-issueSkill
- use-case-designSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 33
Don't fix anything without the user asking.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Diagnosis
!java "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/ArchHook.java" doctor 2>&1
AI files
!find "${CLAUDE_PROJECT_DIR:-.}/.claude" -maxdepth 2 -type f | sort
Interpret the result above and tell the user, in two or three sentences, whether the setup is operational. If something is marked with ❌, give the concrete command that fixes it — don't describe the problem in general terms.
The Provenance line is the one exception to "give the command": when it lists files
edited locally, say which ones and that an update would overwrite them. Don't offer to
run the update — losing a hand-edited norm is the user's call, not a fix to apply.
Don't fix anything without the user asking.
Why this is a manually-invoked skill
Form 2: the whole body is two shell injections plus how to read them, so it is a
procedure (axis 5) fired by a person who wants a verdict (axis 2 — /arch-doctor). Form 1
was rejected because a diagnostic the model reaches on its own runs a JVM and a find on
every session that mentions a hook; Form 3 was rejected because there is nothing to isolate —
the output is the report, and it is what the user asked to see.
Runs on sonnet with effort: high: the report is computed, but naming the cause and the
command that fixes it is judgment (@.claude/decisions/0080-procedural-skills-on-sonnet.md).
The name is not doctor: /doctor is a native command, and a skill folder with that name
shadows it silently — @CLAUDE.md § Known pitfalls.
Contract
Class: observer — the territory is skill_classes.observer in
@.claude/schemas/extensions.json, and it is empty: this skill writes no file. It
reports, and the fix is the user's call. ArchHook.java guard enforces it.
Reads the output of ArchHook.java doctor (which folds in compose) and the listing of
.claude/, both injected above. Nothing else: an injection that lied about the setup would
be worse than no report.
Writes nothing, ever. Leaves no audit report either — its class, observer in
skill_classes of @.claude/schemas/extensions.json, declares audited: false, because an
observer that records its own observation makes the trail mostly about reading 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.

