Review Vikunja database migrations for cross-DB safety and error handling.
npx skills add https://github.com/go-vikunja/vikunja --skill migration-go-vikunja
Please help me install this Agent Skill. Skill: migration Source: https://github.com/go-vikunja/vikunja/tree/main/.claude/skills/migration Command: npx skills add https://github.com/go-vikunja/vikunja --skill migration-go-vikunja
This Skill helps prevent broken or unsafe Vikunja database migrations by guiding developers to write cross-DB, production-safe migration code that handles errors correctly and avoids schema/data inconsistencies.
tx.Exec, session.Exec, and xorm calls so migrations do not falsely appear successful.time.Time for time fields and requires struct and frontend model sync after schema changes.mage test:feature (SQLite default) to catch schema/behavior mismatches after changes.Ask the AI to review or generate a new Vikunja migration for your struct change, ensuring cross-DB compatibility, strict error handling, correct time field usage, and updated frontend model types.
High-intent search queries and answers about installing and using this skill.
Database migrations across MySQL, PostgreSQL, and SQLite require strict error handling for all DDL execution and explicit cross-DB type-safety considerations to prevent silent failures and schema inconsistencies.
Migrations falsely appear successful when errors from tx.Exec, session.Exec, and xorm calls go unhandled. Enforcing strict DDL error handling discipline catches these execution failures and prevents false success reports.
Time-column updates require enforcing time.Time for time fields and synchronizing struct and frontend models after schema changes to maintain consistency across the application layer.
Sanitizing user-supplied paths and archive entry names in migration logic prevents directory traversal and misuse. This safety measure is required when import data touches user-supplied file paths.
Running mage test:feature with SQLite as the default database validates schema and behavior consistency after migration changes, catching cross-DB mismatches before deployment.
Cross-DB schema evolution without explicit type-safety considerations risks broken migrations and data inconsistencies across MySQL, PostgreSQL, and SQLite due to differing native type behaviors and DDL execution rules.
OriginHubAIVerify code quality with linting, type checks, and tests before committing.
Prompt-or-Die-LabsGenerate and apply Drizzle Kit migrations for PostgreSQL or SQLite schema changes.
GlowLEDAudit Drift table definitions, migrations, and repository mappings against domain models.
yunqiqiliangDocument ClickZetta Lakehouse SQL syntax for DDL, DML, and DQL migrations.