migrate-sources

Migrate legacy Wiki/sources/*.md files to the current source-stub format.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/kaneyxx/paper-wiki --skill migrate-sources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-sources
Source: https://github.com/kaneyxx/paper-wiki/tree/main/skills/migrate-sources
Command: npx skills add https://github.com/kaneyxx/paper-wiki --skill migrate-sources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading legacy Wiki/sources entries to the current source-stub format can be error-prone and labor-intensive, risking content drift.

Core Features & Use Cases

  • Preserves user-edited content in Notes, Key Takeaways, and Figures while upgrading structure.
  • Automates batch migration of Wiki/sources/*.md files to the current schema with idempotent rewrites.
  • Dry-run and confirmation workflow to preview changes before applying them, plus post-migration health checks.

Quick Start

Run the migrate-sources workflow to upgrade all Wiki/sources/*.md files while preserving your notes.

Frequently Asked Questions about migrate-sources

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

FAQPage Schema
How do I upgrade legacy markdown sources to a new format without losing notes and figures?

Batch migrating wiki sources to a current schema is done by rewriting legacy Wiki/sources/*.md files while preserving user-edited content in Notes, Key Takeaways, and Figures. Idempotent rewrites ensure consistent formatting across all source files safely.

Can I preview source file migration changes before applying them to my wiki?

Yes, you can preview source file migration changes before applying them by using the dry-run mode. This allows you to review all proposed formatting updates to your markdown files and confirm them before any actual rewrites occur.

What happens to user-edited Key Takeaways when upgrading wiki source files?

User-edited Key Takeaways are preserved when upgrading wiki source files. The migration targets and rewrites the structural schema of legacy markdown files while explicitly protecting your manually added content in Notes, Key Takeaways, and Figures.

How do I check wiki source formatting health after completing a markdown migration?

Checking wiki source formatting health after completing a markdown migration is handled by built-in post-migration health checks. The workflow automatically runs wiki-lint and wiki-compile to validate that all source files conform to the updated schema.

Does the wiki source migration workflow support batch processing for multiple markdown files?

Yes, the wiki source migration workflow supports batch processing for multiple markdown files. It automates the batch migration of all Wiki/sources/*.md files to the current source-stub format using idempotent rewrites for consistent results.