Run any Skill in Manus with one click

lumi-check

Stars34

Forks14

UpdatedJuly 18, 2026 at 01:47

Run lint.mjs --json, summarize findings by severity, offer to apply --fix for auto-fixable checks (L01/L03/L06/L07/L09), self-check re-run to confirm 0 errors, and surface advisory warnings for user attention. Use this whenever the user asks to "check the wiki", "run lint", "verify the graph", "are there broken links?", "what's wrong with the wiki?", "health check", or "are there missing reverse links?". Also fires for: weekly review requests, before committing wiki changes, after a bulk ingest session, or any time the user wants to know the structural state of the wiki.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

tronghieu

tronghieu/lumina-wiki

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

More from this repository

same repository

lumi-edit

tronghieu/lumina-wiki

Guided wiki page authoring and refactoring: apply user-directed edits to a wiki page with schema validation and bidirectional-edge integrity preserved. Use this whenever the user asks to update, fix, revise, rewrite, correct, or clean up a wiki page — even if they don't say "edit". Also fires for: "fix the reverse link on X", "update the summary for Y", "set importance to 4 on Z", "the lint check found a missing link in ...", or any request that modifies one wiki page without ingesting a new source.

2026-07-1834

lumi-ingest

tronghieu/lumina-wiki

Turn a raw source file into structured wiki pages: source page, concept and person stubs, wiki.mjs-managed graph edges, citation edges, and a log entry. Pauses at four checkpoints (draft, lint, verify, finalize) so you can review before the work is committed to the wiki — accept, revise, or quit at any checkpoint without losing progress. Resumable across sessions. Use this whenever the user says "ingest", "add", "file", "process", "summarize into the wiki", "create a wiki page for", or drops a filename from raw/sources/. Also fires for: "I added a PDF to raw/sources/", "add this paper to the wiki", "parse this article", "what should I do with raw/sources/X?", or any request to bring a new source into the wiki graph. Also accepts Mode B input — paper title, arxiv ID, or URL, without a local file path. Examples: "ingest paper 2604.03501v2", "ingest arxiv:2604.03501", "ingest https://arxiv.org/abs/2604.03501". The skill fetches the PDF automatically in that case. Also handles whole books, theses, and other 50+ p

2026-07-0734

lumi-verify

tronghieu/lumina-wiki

Check that wiki notes match the sources they cite. Flags statements that appear in a wiki page but are not supported by the cited material, statements that contradict other parts of the same page, and (with --external) statements contradicted by current web search results. Reports findings for the user to review; never edits notes automatically. Run on one page (`/lumi-verify <slug>`), the whole wiki (`/lumi-verify --all`), or only recently-changed pages (`--since <date>`). Use after AI adds new wiki pages, before sharing or exporting the wiki, or as a periodic health check on older pages. Trigger on phrases like "verify", "fact-check the wiki", "is this page accurate?", "check sources", "retro verify". Operates on sources/* pages in v0.9; other page types are skipped.

2026-07-0734

lumi-reading-chapter-ingest

tronghieu/lumina-wiki

Ingest one book chapter into the wiki and extract character mentions, theme tags, and plot beats into the graph. Use whenever the user wants to ingest, file, or process a chapter — including phrasings like "I just finished chapter 3", "add this chapter to the wiki", "file chapter 2 of [book]", or "track what happened in chapter 5".

2026-07-0734

lumi-ask

tronghieu/lumina-wiki

Answer questions from what the wiki already knows, citing the wiki pages behind every claim so the user can open and verify them. Reads only — never changes the wiki unless the user explicitly asks to save the answer as a page. Use this whenever the user asks a question whose answer should come from the wiki — even if they don't say "ask". Also fires for: "what does the wiki say about X", "compare X and Y from what we've ingested", "summarize the wiki's coverage of X", "what concepts relate to Y", "find all sources that mention Z", "what have we learned about X", or any synthesis or retrieval request over accumulated wiki content. If a question could be answered from raw/ but isn't in the wiki yet, surface the gap, list the matching raw/ files so the user can open them directly, and suggest /lumi-ingest instead of reading raw/.

2026-07-0534

lumi-init

tronghieu/lumina-wiki

Bootstrap a fresh Lumina wiki workspace: verify config, materialize directory structure, seed wiki/index.md and wiki/log.md, and write the first log entry. Use this whenever the user says "initialize the wiki", "set up the wiki", "I just ran lumina install", "the wiki is empty", "start fresh", or "create the wiki structure". Also fires for: "wiki/index.md is missing", "the directories don't exist yet", or any first-run scenario after lumina install. Run once per workspace. Safe to re-run (idempotent).

2026-07-0234

name	lumi-check
description	Run lint.mjs --json, summarize findings by severity, offer to apply --fix for auto-fixable checks (L01/L03/L06/L07/L09), self-check re-run to confirm 0 errors, and surface advisory warnings for user attention. Use this whenever the user asks to "check the wiki", "run lint", "verify the graph", "are there broken links?", "what's wrong with the wiki?", "health check", or "are there missing reverse links?". Also fires for: weekly review requests, before committing wiki changes, after a bulk ingest session, or any time the user wants to know the structural state of the wiki.
allowed-tools	["Bash","Read"]

/lumi-check

If you were spawned in the same session that just ran /lumi-ingest, surface a one-line note to the user suggesting they re-run this check in a fresh session or via a subagent for an independent read — then proceed normally. Same model with blank context catches bias from the reasoning chain that built the pages you are now reviewing.

Role

You are the wiki's quality gate. You run the linter, classify findings, apply safe fixes with a self-check re-run, and surface the issues the user must resolve manually. You do not decide what is correct content — you enforce structural and graph-integrity rules.

Context

Read README.md at the project root before this SKILL.md. The Cross-Reference Rules section defines the bidirectional-link invariant this check enforces. The Constraints section lists the non-negotiable rules.

Key workspace paths:

_lumina/scripts/lint.mjs — the linter; always call with --json
_lumina/config/lumina.config.yaml — bidirectional exemption globs
wiki/log.md — log the check result here

Read references/lint-checks.md before classifying findings or explaining which checks are auto-fixable.

Instructions

Step 1 — Run lint in read mode

node _lumina/scripts/lint.mjs --json

Do not pass --fix on the first pass. Read the JSON output to understand the full scope before applying any changes.

JSON output shape:

{
  "schema_version": "0.1.0",
  "scanned_files": <number>,
  "checks_run": ["L01","L02",...],
  "findings": [
    {
      "id": "<check-id>-<slug>",
      "severity": "error"|"warning"|"info",
      "fixable": true|false,
      "file": "sources/lora.md",
      "line": 12,
      "message": "...",
      "fix_applied": false,
      "proposed_fix": "..."
    }
  ],
  "summary": { "errors": N, "warnings": N, "info": N, "fixes_applied": 0 }
}

Step 2 — Classify findings

Group findings using references/lint-checks.md: errors first, then advisory warnings. Surface warnings even when summary.errors === 0.

Step 3 — Offer to apply fixes

If there are auto-fixable findings, tell the user what will be fixed and ask for confirmation:

"I found fixable findings. I can auto-fix the following:

L06 (missing reverse edge):
L09 (index out of sync) Shall I apply --fix?"

If the user confirms (or runs /lumi-check --fix directly):

node _lumina/scripts/lint.mjs --fix --json

The --fix pass:

Applies the supported auto-fixes listed in references/lint-checks.md (L01, L03, L06, L07, L09)
Leaves every other check (L02, L04, L05, L08, L10, L11, L12, L13, L14, L16, L17) for manual correction

Step 4 — Self-check re-run

After applying fixes, re-run lint to confirm the error count reached 0:

node _lumina/scripts/lint.mjs --json

If errors remain, do not report done. Address each remaining error specifically:

If L06 persists after --fix, the reverse edge target may not exist yet. Identify the missing page and suggest /lumi-ingest or /lumi-edit to create it.
If L01 persists, the placeholder inserted by --fix may have the wrong type. Use wiki.mjs set-meta to correct it:
```
node _lumina/scripts/wiki.mjs set-meta <slug> <key> "<value>"
```
If L02, L05, L08, or L10 remain, report the exact fields, wikilinks, edges, or alias conflicts that need manual correction.
If L13 or L16 persist, suggest /lumi-migrate-legacy --backfill-ids — these are not fixed by lint.mjs --fix.
If L17 (dangling edge) persists, the edge still points at a slug with no wiki file. Run wiki.mjs remove-edge <from> <type> <to> to drop it, or recreate the missing page if the relationship should still hold.

Repeat until summary.errors === 0. Do not loop more than 3 times — if errors persist, surface them to the user as needing manual attention.

Step 5 — Log the check

node _lumina/scripts/wiki.mjs log check "<N> errors fixed, <M> warnings advisory. <N2> errors remain."

Output Format

Present findings in a structured list. Group errors first, then warnings.

Lint check: <scanned_files> files scanned

Errors (N):
  concepts/positional-encoding.md:18 — a return link is missing, pointing back to sources/attention-revisited (L06)
  summary/transformers-overview.md:42 — a link points to a page that does not exist: [[flash-decoding]] (L05)

Warnings (M, advisory):
  concepts/rotary-embeddings.md — this page has no inbound or outbound links yet (L04)
  wiki/index.md — the page catalog is out of date (L09)

Fixes available: L06, L09 (N total). Apply? [yes/no]

After fix + re-run:

Fixed N errors. Re-run: 0 errors, M warnings.
Log entry written.

Examples

User: "Run a lint check."

Normal case — clean wiki with only advisory warnings:

node _lumina/scripts/lint.mjs --json
# → { "summary": { "errors": 0, "warnings": 2, ... } }

Report: "0 errors. 2 advisory warnings: [list]. No fixes needed." Log: check | 0 errors, 2 warnings advisory.

User: "/lumi-check --fix" (or user confirms fix after seeing the plan)

Normal fix path — missing reverse edges:

node _lumina/scripts/lint.mjs --json
# → 3 L06 errors; show the user the file list
# User confirms
node _lumina/scripts/lint.mjs --fix --json
# → 3 fixes applied
node _lumina/scripts/lint.mjs --json
# → 0 errors (self-check re-run confirms)
node _lumina/scripts/wiki.mjs log check "3 L06 errors fixed. 0 errors remain."

The self-check re-run is non-negotiable — do not report "fixed" until lint confirms 0 errors.

User: "Check the wiki and auto-fix everything without asking me."

Guardrail escalation — user wants silent auto-fix: Never apply --fix without first showing what will change. Explain what the fix list contains and ask for confirmation. This protects against file renames and index rewrites the user may want to review first.

Guardrails

Always run lint --json (read-only) before running lint --fix. Never apply fixes without showing the user what will change.
Do not modify wiki/ directly during this skill — all mutations go through lint.mjs --fix (which uses atomic writes internally).
Do not suppress warnings as noise. Surface every advisory so the user is aware.
The self-check re-run is non-negotiable. Reporting "fixed" without a confirming lint pass is not acceptable.

Definition of Done

Before reporting done, verify:

(a) node _lumina/scripts/lint.mjs --json shows summary.errors === 0 (b) wiki/log.md has a new ## [YYYY-MM-DD] check | ... entry (c) Running /lumi-check again immediately after produces the same 0-error result (no regressions from the fix pass)