myco:vault-schema-migration

Apply versioned migrations to the Vault SQLite schema.

12|2|Updated Mar 15, 2026

Search Tags:#versioning #schema #migration #sqlite #vault #databases #backfill

Ready to run

npx skills add https://github.com/goondocks-co/myco --skill myco-vault-schema-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: myco:vault-schema-migration
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/vault-schema-migration
Command: npx skills add https://github.com/goondocks-co/myco --skill myco-vault-schema-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely migrate the vault SQLite schema by introducing versioned migrations, preventing data loss or corruption across upgrades.

Core Features & Use Cases

Add new versions to the migration chain safely, with idempotent checks to avoid re-applying migrations.
Write and apply safe SQL migrations (ALTER TABLE, CREATE TABLE) with optional backfill steps to populate new fields.
Verify migrations end-to-end in a test vault and update the SCHEMA_VERSION constants accordingly.

Quick Start

Walk me through adding a new schema version, implement the migration block, and verify in a test vault.

Frequently Asked Questions about myco:vault-schema-migration

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

FAQPage Schema

How do I safely migrate a SQLite database schema without losing data?▼

Safe SQLite schema migration requires applying versioned migrations with idempotent checks to prevent data loss. You add a new migration block, update the SCHEMA_VERSION constant, perform any necessary data backfills, and verify the migration end-to-end in a test vault before deployment.

What is the best way to handle schema backfills when adding columns to an existing SQLite vault?▼

The best way to handle schema backfills is to include optional backfill steps within your versioned migration block. This ensures new fields are populated correctly while applying safe SQL migrations like ALTER TABLE, preventing data corruption across single-user and multi-device vaults.

Does this schema migration process work for multi-device vault deployments?▼

Yes, the schema migration process explicitly targets both single-user and multi-device vault deployments. It applies versioned migrations and idempotent checks to ensure data consistency and prevent corruption across all synchronized vault instances during upgrades.

How do I add a new schema version to the migration chain?▼

To add a new schema version to the migration chain, you update the SCHEMA_VERSION constants and write a new migration block. This block contains safe SQL statements like ALTER TABLE or CREATE TABLE, including any required backfills, to transition the database safely.

Why do I need idempotent checks when applying SQL migrations to a vault?▼

Idempotent checks are required when applying SQL migrations to prevent re-applying migration blocks that have already been executed. This avoids duplicate column errors, data overwrites, and corruption, ensuring safe upgrades across single-user and multi-device vault deployments.