migrate

Migrate wiki schemas across plugin version upgrades with backups and validation.

20|2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/ignromanov/llm-obsidian-wiki --skill migrate-ignromanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/ignromanov/llm-obsidian-wiki/tree/main/skills/migrate
Command: npx skills add https://github.com/ignromanov/llm-obsidian-wiki --skill migrate-ignromanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps wiki vaults compatible with plugin updates by applying structural migrations, validating compatibility, and ensuring vault metadata stays up to date.

Core Features & Use Cases

  • Detects plugin version changes and applies migration chains (v<from> to v<to>)
  • Creates backups and validates results
  • Uses wiki-health and migration agent for consistency and safety

Quick Start

Migrate my wiki schema to the latest plugin version after upgrading.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I migrate my wiki schema after updating a plugin?

You can migrate your wiki schema by triggering a migration flow that detects plugin version changes and applies the necessary structural updates. The skill creates backups, runs script-driven migrations, and validates results to ensure vault compatibility.

When do I need to run a wiki schema migration?

You need a wiki schema migration when a plugin update introduces structural changes that affect vault compatibility. The skill detects these plugin version changes and applies the required migration chain to keep vault metadata up to date and prevent compatibility issues.

Does the migration process create a backup before updating the vault schema?

Yes, the schema migration process creates backups before applying any structural updates. It enforces deterministic safety checkpoints and performs post-migration validation to ensure your wiki vault remains in a compliant state throughout the plugin upgrade.

How does the schema version validation work after a plugin upgrade?

Schema version validation works by running post-migration checks to confirm vault consistency after updating the schema_version. The skill uses a wiki-health agent to validate compatibility and guarantee the vault meets the new plugin version's structural requirements.

Can I use this to migrate wiki schemas across multiple plugin version jumps?

Yes, you can migrate wiki schemas across multiple plugin version jumps. The skill detects version changes and applies a full migration chain from the starting version to the target version, executing intermediate scripts and safety checkpoints to reach a compliant state.