Lint
July 1, 2026 · View on GitHub
Lint is the periodic health-check that keeps a compounding artifact from drifting. Karpathy is emphatic that the lint pass is not optional — drift (stale claims, orphans, silent contradictions) is the main way an LLM Wiki degrades over time.
Checks
Drawn from the pattern and the the personal work wiki's lint skill:
- Schema compliance — every concept has parseable
frontmatter with a non-empty
type. (This is the conformance bar.) - Contradictions — concepts that assert conflicting facts.
- Stale claims — statements a newer source has superseded; stale overviews behind their children.
- Orphan concepts — pages with zero inbound links.
- Missing cross-references — concepts that discuss the same entity/theme but don't link.
- Coverage gaps — entities mentioned repeatedly across concepts but lacking their own page; data gaps worth a web search.
- Broken links — link targets that don't exist. Per §5.3/§9 these are a health signal only and never invalidate the bundle — a broken link may just mark unwritten knowledge.
Output
Report findings grouped by check, with severity (error / warning / info). Optionally auto-fix what is safe (stale overviews, missing cross-links) and flag the rest. Append a summary to the log. A good lint pass also suggests new questions to investigate and new sources to seek — turning maintenance into a source of new ingest and query work.