lint-wiki

Run twelve wiki vault health checks and produce a severity-ordered report.

Updated Oct 10, 2023
One-click install
npx skills add https://github.com/kirakuiin/note --skill lint-wiki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-wiki
Source: https://github.com/kirakuiin/note/tree/main/Obsidian%20Vault/9-Meta/Skills/lint-wiki
Command: npx skills add https://github.com/kirakuiin/note --skill lint-wiki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain wiki quality by scanning the vault for twelve health checks and generating a structured, severity-ordered report; fixes require explicit user confirmation before any modification.

Core Features & Use Cases

  • Phase 1: Run all checks and collect affected files and issue descriptions without modifying any content.
  • Phase 2: Produce a severity-ordered report (Critical > Warning > Suggestion) to guide remediation.
  • Phase 3: Provide actionable insights for issues such as broken wikilinks, orphan pages, missing frontmatter, visibility mismatches, cross-boundary references, index drift, duplicates, stale claims, missing concepts, stale projects, wild tags, and redline tag leaks, with recommended fixes awaiting user approval.

Quick Start

Use the lint-wiki workflow to audit vault health and generate a severity-ordered report.

Frequently Asked Questions about lint-wiki

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my wiki vault for broken links and missing frontmatter?

You can audit wiki vault health by scanning for broken wikilinks, missing frontmatter, orphan pages, and index drift. The tool collects affected files and generates a structured report without modifying content initially.

What is the best way to audit wiki health after a large-scale migration?

The best way to audit wiki health after a migration is to run a comprehensive validation check across the vault. It enforces twelve specific checks including visibility mismatches and stale claims, producing a severity-ordered report to guide remediation.

Does the wiki lint process automatically fix orphan pages and broken wikilinks?

No, the wiki lint process does not automatically fix issues. It provides actionable insights and recommended fixes for problems like orphan pages and broken wikilinks, but all updates are gated behind explicit user confirmation before any modification occurs.

How does a wiki health check report organize issues by severity?

A wiki health check report organizes issues by severity using a three-tier system: Critical, Warning, and Suggestion. This severity-ordered structure helps prioritize remediation of major issues like broken links over minor suggestions like wild tags.

What specific issues does a wiki structure validation check identify?

Wiki structure validation identifies twelve specific issues including broken wikilinks, orphan pages, missing frontmatter, visibility mismatches, cross-boundary references, index drift, duplicates, stale claims, missing concepts, stale projects, wild tags, and redline tag leaks.

When should I run a wiki lint audit on my vault?

You should run a wiki lint audit after large-scale edits, vault migrations, or as a periodic health check. This ensures structural integrity by catching issues like index drift and duplicate pages before they compound across the wiki.