docs-checkerlisted

# Docs Checker Audit the repository's context files — `CLAUDE.md` at any depth, the `.claude/` tree (skills, rules, commands), READMEs, and the docs tree — for correctness. This is a **conservative audit**: report findings with evidence, do not rewrite anything unless the user asks. Style, tone, and level of detail are the author's choices and are out of scope. ## Prerequisites - Node.js >= 22 (the bundled script uses `fs.globSync`) ## Workflow ### 1. Deterministic pass Run the bundled checker from the repo root: ```bash node ${CLAUDE_SKILL_DIR}/scripts/docs-check.mjs $ARGUMENTS ``` It needs no config and no dependencies. What it does: - Checks relative/absolute markdown links and image assets against the working tree - Checks backticked source paths in prose (`src/foo.ts`, `@alias/bar`) against the codebase, resolving tsconfig/package.json aliases - Scans the paths you name (or the repo's docs tree by default), plus every `CLAUDE.md` and the whole `.claude/` tree automatically - Cross-repo docs: pass `--repo=NAME:DIR` for each sibling checkout the docs reference Exit 0 is clean, 1 means findings (printed as `line:col rule message` with did-you-mean hints), 2 is bad invocation. Its findings are ground truth — do not second-guess them. ### 2. Semantic pass Read the context files the script scanned — but keep this pass on a **scoped diet**: `CLAUDE.md` files, the `.claude/` tree, and top-level READMEs. Do not crawl the whole docs tree unless the user asked; the scri