axiom-database-migration

Plan additive SQLite, GRDB, and SwiftData migrations.

3|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/harivansh-afk/claude-code-vertical --skill axiom-database-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-database-migration
Source: https://github.com/harivansh-afk/claude-code-vertical/tree/main/skill-index/skills/axiom-database-migration
Command: npx skills add https://github.com/harivansh-afk/claude-code-vertical --skill axiom-database-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safe database schema evolution is critical for production apps. This Skill provides tested patterns and guidance to perform additive, idempotent migrations without risking data loss across SQLite/GRDB/SwiftData environments.

Core Features & Use Cases

  • Additive migrations: safely add columns or tables without dropping data.
  • Immutable migrations: treat shipped migrations as final; plan new migrations for changes.
  • Validation & testing: verify upgrade paths from older versions to newer ones, including data preservation.
  • Real-world guidance: handle NOT NULL constraints, foreign keys, and type changes with safe strategies.

Quick Start

Start by inspecting existing migrations, and plan a new migration that adds a nullable column, then backfill as a separate step. For example, ask the model: "How do I add a nullable column to users without disturbing existing rows?"

Frequently Asked Questions about axiom-database-migration

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

FAQPage Schema
How do I add a NOT NULL column to an existing SQLite table without losing user data?

To add a NOT NULL column without data loss, perform an additive migration by first adding a nullable column, then backfilling the existing rows with default values as a separate step before enforcing the constraint.

What is an idempotent database migration and how does it protect SQLite data?

An idempotent database migration is a transactional schema change that can be applied repeatedly without causing errors or data loss, ensuring safe upgrades across iOS and macOS apps by preserving existing user data.

Can I use this approach to manage schema changes for SwiftData and GRDB?

Yes, these safe, additive migration patterns apply directly to SQLite, GRDB, and SwiftData environments, providing tested guidance for schema evolution in iOS and macOS apps while preserving user data.

What is the best way to handle foreign key constraints during a database migration?

The best way to handle foreign key constraints is using immutable, additive migrations that enforce transactional and safe patterns, allowing you to plan new migrations for changes rather than altering shipped ones.

How do I validate a database upgrade path from an older schema version to a newer one?

You validate a database upgrade path by testing the migration sequence to verify data preservation and ensure that additive, transactional migrations correctly transition older schemas to newer versions without data loss.