lumi-check

Runs the wiki linter, classifies findings by severity, and applies confirmed auto-fixes with a verification re-run.

Updated Jun 3, 2026

Search Tags:#markdown #knowledge base #auto-fix #wiki #lint #frontmatter #link validation

Ready to run

npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill lumi-check-mathematicguy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lumi-check
Source: https://github.com/MathematicGuy/team-006-vin20k/tree/main/lumina-wiki/.agents/skills/lumi-check
Command: npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill lumi-check-mathematicguy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Maintaining a structured markdown wiki with bidirectional links, frontmatter rules, and an index catalog is error-prone; this Skill runs the lint.mjs checker, interprets its JSON findings, and safely applies auto-fixes so the wiki stays structurally consistent. ## Core Features & Use Cases - Lint execution and classification: Runs `node _lumina/scripts/lint.mjs --json`, groups findings into errors (L01/L02/L03/L05/L06/L08) and advisory warnings (L04/L07/L09) using the lint-checks reference. - Confirmed auto-fixing with self-check: Applies `--fix` only after showing the user what will change, then re-runs lint to confirm zero errors before reporting done. - Audit logging: Writes a dated check entry to `wiki/log.md` after every run. - Use Case: After a bulk ingest session, ask for a wiki health check to find missing reverse links and broken wikilinks, review the fix plan, and confirm the auto-fix pass. ## Quick Start Ask the assistant to run a lint check on the wiki and fix any auto-fixable errors after showing you the plan.

Frequently Asked Questions about lumi-check

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

FAQPage Schema

How do I check a markdown wiki for broken links and missing reverse edges?▼

Run the lint script with `node _lumina/scripts/lint.mjs --json` to get structured findings. The output lists each issue with a check ID, severity, file, and line, so you can classify errors versus advisory warnings before fixing.

Which wiki lint errors can be auto-fixed?▼

The linter's --fix mode handles L01 (missing frontmatter field), L03 (non-kebab slug), L06 (missing reverse edge), L07 (duplicate symmetric edge), and L09 (stale index). L02, L05, and L08 require manual correction by the user.

Why does the L06 missing reverse edge error persist after running --fix?▼

L06 persists when the reverse edge target page does not exist yet. Identify the missing page from the finding and create it first, then re-run the lint check to confirm the error clears.

Can the linter auto-fix everything without asking for confirmation?▼

No. The workflow always runs a read-only --json pass first and shows the planned changes before applying --fix. This guardrail protects against unwanted file renames and index rewrites.

How do I verify wiki lint fixes actually worked?▼

Re-run `node _lumina/scripts/lint.mjs --json` after the fix pass and confirm summary.errors equals 0. The result is also logged to wiki/log.md as a dated check entry for audit purposes.