Lint

---
description: Lint the vault — validate frontmatter, wiki-links, enums, and structure
allowed-tools: Bash, Read, Edit, Grep, Glob
---

# /lint — vault validation workflow

Your job is to validate the vault and report/fix issues per `_meta/SCHEMA.md` §10.3.

## Steps

1. **Run the automated linter:**
   ```bash
   python3 scripts/lint.py

2. Run linter tests:

   python3 -m pytest tests/ -q
   

3. If 0 errors and tests green: report to user and finish.

4. If errors or warnings found:

   • Show the report to the user grouped by file.
   • Propose concrete fixes for each issue:
     • Broken wiki-links → create missing page or fix the link
     • Missing required fields → add with reasonable value
     • Invalid enums → correct to canonical value per §6
     • Orphan pages → suggest adding inbound links
   • Do NOT apply fixes without user approval.

5. On approval, apply fixes with Edit and re-run linter to verify. Iterate until 0 errors.

6. Manual semantic checks (beyond what the script catches):

   • Contradictions between pages
   • Concepts mentioned in text but lacking their own page
   • Claims without source citations
   • Stale pages (last_updated > 90 days)
   • _inbox/ files older than 7 days

7. If changes were made, propose commit:

   git commit -m "lint: <short summary of fixes>"
   

Rules

• The linter script is the source of truth for automated validation.
• If a linter rule seems wrong, discuss with the user first — don't silently modify scripts/lint.py.
• All tests must stay green after fixes.