← ClaudeAtlas

rite-doctorlisted

Doctor DevRites setup or index health. Use when workflow wiring is broken, the user asks to check DevRites, or says "reindex". Not for application bugs.
ViktorsBaikers/DevRites · ★ 1 · AI & Automation · score 63
Install: claude install-skill ViktorsBaikers/DevRites
# /rite-doctor: health check The on-demand deep report. The same checks run **silently at session start** (the orient hook surfaces issues only when there are any); `/rite-doctor` runs them **verbosely**: printing every check, pass or fail, so you can inspect health even when nothing is broken. It covers version drift, Claude Code wiring, optional Codex mirrors/hooks, stale host artifacts, and missing install markers when those files are present. With `--code`, it also runs the read-only project code-health dashboard (`devrites-engine health`). It also reports an in-progress git merge/rebase and points to `git-workflow.md`'s conflict recovery playbook. It is **read-only**: it never edits the workspace, never advances a phase, never blocks. ## Workflow 1. Run the diagnose core verbosely (resolve across install layouts): ```bash devrites-engine doctor; echo "doctor rc=$?" ``` 1a. **Surface the learnings nudge**: point the user at `/rite-learn` when a pattern recurs across shipped features (read-only; silent when there's nothing to say): ```bash devrites-engine learnings nudge ``` 1b. **Code-health dashboard (only when `$ARGUMENTS` includes `--code`).** Run the read-only check and surface the PASS/WARN/FAIL table; it appends `.devrites/health.jsonl` for trends and never blocks doctor: ```bash devrites-engine health; echo "health rc=$?" ``` 1c. **Validate project extensions + overrides** (read-only: report, don't sync). A user rite/ reviewer un