docs-doctor

# Docs Doctor Audit a repository's documentation like a doctor: triage what's missing, wrong, stale, structurally broken, or written badly. Produce a severity-ranked report; optionally apply low-risk fixes. Configurable by mode, scope, and template profile. Learns from your feedback over time. ## Preferences _On startup, use the `Read` tool to load `~/.claude/skills/docs-doctor/preferences.md`. If missing, treat as "no preferences set" and continue with Defaults below._ ## Context _On startup, use the `Bash` tool to detect: git repo root (`git rev-parse --show-toplevel`), current branch, and whether `package.json` / `pyproject.toml` / `Cargo.toml` / `go.mod` is present (for code-doc check selection). Use the `Glob` tool to list `**/*.md`, `**/*.mdx`, and any `CLAUDE.md` / `AGENT.md` files. Skip any detection step that fails — do not abort._ ## Command routing Check `$ARGUMENTS`: - **`help`** → display help, then stop - **`config`** → interactive setup, then stop - **`reset`** → delete `~/.claude/skills/docs-doctor/preferences.md`, `feedback-journal.md`, `sessions/`, `resume-state.md`, confirm, stop - **`feedback`** → run the feedback flow (see § Feedback & learning), then stop - **`templates`** → list available templates from `~/.claude/skills/docs-doctor/templates/`, then stop - **`resume`** → if `resume-state.md` exists, continue the last interrupted run; else say `No session to resume.` - **`--from-template=<name>`** → load template, merge with flags, run - **anyth...