Create forward-only SQLite migrations for Aidog schema changes.
npx skills add https://github.com/lazygophers/aidog --skill aidog-db-migration
Please help me install this Agent Skill. Skill: aidog-db-migration Source: https://github.com/lazygophers/aidog/tree/main/.claude/skills/aidog-db-migration Command: npx skills add https://github.com/lazygophers/aidog --skill aidog-db-migration
This Skill removes the risk and guesswork from changing Aidog's local SQLite schema, especially when you need to add tables, add columns, change constraints, split fields, or rebuild tables without breaking existing user databases.
Ask the assistant to create the next Aidog SQLite migration for a specific schema change and update the related Rust database code paths in sync.
High-intent search queries and answers about installing and using this skill.
To add a UNIQUE constraint in SQLite, you must use a table rebuild pattern. This involves creating a new table with the desired schema, copying data while filtering conflicting legacy rows, and preserving indexes during the rebuild to safely evolve the schema.
A forward-only SQLite migration uses numbered, append-only SQL files without a rollback path. You need this approach for embedded database upgrades to preserve existing user data and safely handle legacy rows automatically during startup.
To split a column in SQLite, use a rebuild-table pattern to rename and restructure the fields. You must synchronize updates to the database code paths and related models to ensure existing installations continue working during the startup migration.
Yes, you must add DEFAULT values for new columns when evolving an SQLite schema. This compatibility safeguard ensures the migration remains idempotent and prevents errors when existing legacy rows are upgraded automatically at startup.
The best way to automate embedded SQLite schema changes is applying numbered, forward-only SQL migrations at startup. This safely evolves the schema, handles legacy rows, and preserves user data without requiring manual intervention.
Adding a new schema field requires updating Rust database code paths to maintain synchronization between the database and the application. This ensures the embedded SQLite migration runs correctly and the application models reflect the new schema constraints.
ahtavarasmusGenerate, apply, and rollback Diesel migrations for SQLite or PostgreSQL schemas.
paleoterraValidate SQLite migrations and schemas with sqlite_validator.py CLI commands.
freedomw1987Add new columns to existing Prisma models in production PostgreSQL databases.
matt-rileyDetect migration contracts and outline safe apply, rollback, and recovery plans.
