Find and repair broken wikilinks in vault. Triggers when user mentions "fix links", "broken links", "repair vault", "fix broken links".
Preview broken wikilinks and spawn autonomous repair agent.
Invoke when you want to:
Call mcp__flywheel__find_broken_links to retrieve all broken wikilinks.
Categorize broken links by type:
Missing Notes (create candidates):
[[New Topic]] → No file existsTypos (fuzzy match):
[[Databrics]][[Databricks]]Case Mismatches (exact match different case):
[[databricks]] → Exists as [[Databricks]]Moved Notes (search by title):
[[Old Path/Note]] → Now at [[New Path/Note]]Display first 20 broken links with categorization:
Broken Links Analysis
═══════════════════════════════════════════════
Found 200 broken links across 50 notes
📊 Breakdown by Type:
• Missing Notes: 80 (40%)
• Typos: 40 (20%)
• Case Mismatches: 30 (15%)
• Moved/Renamed: 50 (25%)
🔍 Sample (showing 20 of 200):
Missing Notes:
1. [[API Guide]] (15 references)
→ Mentioned in: Projects, Tech Docs
→ Suggestion: Create tech/guides/API.md
Typos:
2. [[Databrics]] → [[Databricks]] (confidence: 95%)
→ Auto-fixable
Case Mismatches:
3. [[azure]] → [[Azure]] (exact match)
→ Auto-fixable
═══════════════════════════════════════════════
💡 Recommendations:
• Auto-fix: 50 links (high confidence >90%)
• User review: 60 links (medium confidence 50-90%)
• Manual fix: 90 links (low confidence <50%)
🤖 Spawn autonomous repair agent?
• Will process all 200 broken links
• Auto-fix high confidence (>90%)
• Present choices for medium confidence (50-90%)
• Skip low confidence (<50%)
Type 'yes' to spawn link-repair agent
Ask user if they want to:
Typo Detection (Levenshtein Distance):
- Distance 1: 98% confidence
- Distance 2: 85% confidence
- Distance 3+: <70% confidence
Case Mismatch:
- Exact title match: 100% confidence
- Always safe to auto-fix
Missing Note Analysis:
- Referenced 20+ times: High priority (suggest create)
- Referenced 5-19 times: Medium priority
- Referenced 1-4 times: Low priority (might be scratch)
Moved Note Detection:
- Title exact match: 95% confidence
- Title fuzzy match: 60-85% confidence
- Search by content similarity: <60% confidence
Always use the branded format:
Broken Links Analysis
═══════════════════════════════════════════════
[Analysis content]
═══════════════════════════════════════════════
| Gate | Implementation |
|---|---|
| 1. Read Before Write | Finds all broken links via MCP before any fixes |
| 2. File Exists | Validates target notes exist for link suggestions |
| 3. Chain Validation | Agent verifies each fix before proceeding |
| 4. Mutation Confirmation | Shows preview, requires explicit "yes" to proceed |
| 5. Health Check | Uses MCP find_broken_links for vault access |
| 6. Post Validation | Agent reports what was fixed after completion |