lumi-migrate-legacy

Backfills missing frontmatter schema fields on legacy wiki entries after version upgrades.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill lumi-migrate-legacy-mathematicguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lumi-migrate-legacy
Source: https://github.com/MathematicGuy/team-006-vin20k/tree/main/lumina-wiki/.agents/skills/lumi-migrate-legacy
Command: npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill lumi-migrate-legacy-mathematicguy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After upgrading a Lumina wiki package, existing entries often lack newly introduced frontmatter fields like provenance and confidence, causing lint errors and inconsistent metadata. This Skill detects those gaps and backfills them with evidence-based inferred values instead of blind defaults. ## Core Features & Use Cases - CHANGELOG-driven migration: Reads ### Migration sections in the CHANGELOG to determine exactly which fields each version introduced, so it works across versions without modification. - Evidence-based inference: Infers provenance from ingest checkpoints and raw file scans, and confidence from inbound citation counts, falling back to conservative values like unverified when evidence is ambiguous. - Verified, idempotent writes: Applies changes through atomic set-meta operations, re-runs lint to confirm zero errors, clears the manifest flag, and logs the migration. - Use Case: After upgrading a wiki to v0.9, run the migration to backfill provenance and confidence on dozens of legacy source entries, convert legacy url fields to urls arrays, and confirm a clean lint report. ## Quick Start Run /lumi-migrate-legacy to detect missing schema fields on legacy wiki entries and backfill them with inferred values.

Frequently Asked Questions about lumi-migrate-legacy

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

FAQPage Schema
How do I migrate legacy wiki entries after a schema upgrade?▼

Run the migration skill, which reads the CHANGELOG's Migration sections to identify newly required fields, infers values from available evidence, and writes them via set-meta. It finishes by re-running lint to confirm zero errors and clearing the legacyMigrationNeeded manifest flag.

How is the confidence field inferred for wiki entries?▼

Confidence is inferred from inbound citation and edge counts: high for three or more inbound references, medium for one or two, low for doubtful content, and unverified as the safe default when no evidence exists. Ambiguous cases always fall back to unverified.

What happens if the CHANGELOG has no Migration section?▼

The skill falls back to the lint finding messages themselves, which name the exact missing fields from L01 and L11 checks. It never fabricates a migration spec and only backfills fields identified by findings.

Is the wiki migration safe to re-run on large wikis?▼

Yes, set-meta writes are atomic and idempotent, so re-running produces zero file changes on an already-migrated wiki. For batches over 30 entries the skill pauses for user confirmation before writing.

Why do L12 raw_paths drift warnings appear after migration?▼

L12 warnings mean a backfilled raw_paths entry points to a file that does not exist or sits under raw/tmp. The migration is not blocked, but the affected entries need the referenced file located or the path corrected.