wiki-lintlisted

Audit and maintain the health of the Dev Brain vault. Use when the user says "lint the wiki", "wiki health check", "audit my notes", "what needs fixing", "clean up the wiki", or wants to find orphaned pages, broken wikilinks, contradictions, stale claims, missing decision/pattern pages, or topic-vocabulary drift. Runs the structural gate first, then the semantic checks it cannot do.
YoniRaviv/dev-llm-wiki · ★ 2 · Code & Development · score 63

Install: claude install-skill YoniRaviv/dev-llm-wiki

# LINT — vault health audit The vault is `{{VAULT_PATH}}`. Read `CLAUDE.md` first — it is the schema this audits against. Two layers: - **Structural** — `.scripts/vault-check.py` already encodes every mechanical invariant. Run it; do not re-implement it by hand. - **Semantic** — everything below. These need judgement and reading, so scope them. **Scope your reads.** Prefer frontmatter-scoped greps and section-anchored reads over full-page reads. Reading every content page to lint it is the failure mode this vault is built to avoid. ## Step 1 — Structural gate ```bash cd {{VAULT_PATH}} && python3 .scripts/vault-check.py ``` Exit 0 means clean. Otherwise it reports, per check: `whitelist`, `plan-gate`, `spine-gate`, `spine-owner`, `prd-purity`, `tracker-state`, `vault-skills`, `secrets`, `today-committed`, `shipped-status`, `broken-links`, `orphans`. `broken-links` and `orphans` only run on a full scan, not in `--staged` (pre-commit) mode — a brand-new project page with no inbound wikilink yet will show up here without having blocked a commit. Link it; do not exempt it. Fix what it reports before going further — a broken link makes half the semantic checks noisy. **Never loosen a check to make it pass.** If a check is genuinely wrong, say so and explain why; its rules are load-bearing, and the same script backs the pre-commit hook. For orphans specifically: link the page from a related page or from `wiki/index.md`. Do not exempt it. ## Step 2 — Topic vocabulary `wi