hurricane0698/zot/zot-vault-review

zot Vault Review

This skill is for periodic maintenance and synthesis of a zot vault.

Use zot-vault-wiki instead when the review turns into a broader compile pass, a feedback-resolution sprint, or a multi-step reorganization across many notes.

Required workflow

1. Resolve the vault path from ZOT_VAULT, then legacy OMEGA_VAULT.
2. Read kb/meta/index.md, kb/meta/log.md, and kb/meta/review.md when present.
3. Run qmd update -c <vault-local-collection> if note files changed since the last review.
4. Run "$ZOT_VAULT/scripts/kb-lint" for a mechanical pass.
5. Identify orphan notes, stale syntheses, duplicated concepts, and missing active-output drills.
6. If the review produced durable insight, file it under kb/wiki/syntheses/ or kb/wiki/queries/.
7. Use "$ZOT_VAULT/scripts/kb-smoke-test" when search or CLI wiring looks suspicious.
8. When the user asks for versioning, review the diff before any commit.
9. If the work stops being a review and becomes a structural rewrite, switch to zot-vault-wiki.

Review outputs to prefer

• weekly synthesis note
• error-pattern note
• "teach it back" drill
• migration suggestions from legacy notes into kb/wiki/**
• retrieval sanity check based on CLI + qmd smoke test

Guardrails

• Do not auto-commit without checking what changed.
• Keep reviews focused on compounding understanding, not vanity metrics.
• If a file may contain secrets, flag it and recommend rotation or removal.
• Prefer review outputs such as backlog trimming, synthesis notes, and drills over broad note surgery.