wiki-lint runs the claude-obsidian lint engine on your vault and explains what it finds. It understands wikilinks, embeds, aliases, heading and block fragments and code fences, and reports dead or ambiguous links, orphan pages, missing frontmatter, empty sections, stale index entries and source or claim ledger violations.
It only observes. Repairs are a separate operation you choose, built as a new reviewed transaction.
What You Get
- A lint report in text or Markdown with paths, lines, targets and counts
- Findings grouped by impact with suggested remediation kept separate from facts
- Path exclusion for scratch folders
- A repair plan for findings you pick, built as a new transaction
- A before and after lint comparison once repairs are applied
Common Use Cases
- Auditing a vault for dead links and orphans before sharing it
- Checking required frontmatter across all pages
- Verifying that source and claim ledgers stay consistent after an ingest
What Makes It Unique
The linter is deterministic and honors gitignore files inside the vault without calling git, skips dot-prefixed folders as Obsidian does, and never writes a report into the vault. Repairs are never automatic: each fix re-reads its target, records the expected hash and applies through the transaction engine.
Under The Hood
The skill is instructions that run the plugin’s Python core script through the shell with the lint command, which reads the vault and prints a report. It does not fetch web pages or write files during linting. Only if you choose repairs does it build and apply a transaction bundle, and that step writes the approved fixes after you approve the plan hash.