Lint Protocol
Type: concept Tags: llm-wiki, claude-code, token-efficiency
Summary
Periodic health checks Claude runs over the wiki to find structural problems, knowledge gaps, and under-connected nodes. Analogous to a code linter but for a knowledge graph.
Trigger
Ask Claude: “Please lint the wiki.”
Steps
- Scan all wiki pages for:
- Broken
[[links]](references to pages that don’t exist) - Missing required fields
- Sparse content (pages with too little information)
- Broken
- Identify under-connected nodes (pages with few or no backlinks)
- Suggest source articles or topics that would fill knowledge gaps
- Optionally web-search to fill in missing factual data
- Log lint results to
wiki/log.md
Frequency
Run as needed — andrej-karpathy suggests periodic lint runs (daily/weekly) to keep the wiki healthy as it grows.
Value
- Keeps the wiki navigable as it scales
- Surfaces blind spots (“I don’t fully understand X — can you grab more articles?“)
- Maintains relationship quality across the graph