rune-db

Provide your schema diff and the Skill generates paired up and down migration files matching your detected ORM, such as Prisma, TypeORM, Django, or Alembic. Empty downgrade functions are blocked, so every migration includes a working rollback path.

The Skill diffs the current schema against the previous version and classifies each change as SAFE or BREAKING. Drops, renames, type changes, and NOT NULL columns without defaults are flagged as BREAKING and require explicit confirmation before migration generation.

Yes, it detects the ORM in use during discovery and generates migration syntax for Prisma, TypeORM, SQLAlchemy/Alembic, Django ORM, ActiveRecord, or raw SQL. If the ORM cannot be determined, it falls back to generic SQL migration format.

Adding a NOT NULL column without a DEFAULT value fails on tables with existing rows because those rows have no value for the new column. The Skill blocks this pattern and explains the failure instead of silently generating a broken migration.

Yes, it scans migration files and raw SQL for string interpolation in queries and flags each finding as SQL_INJECTION_RISK with file and line location. It recommends parameterized queries with bound placeholders instead.

No, the Skill only generates and validates migrations; it never executes them in production. Execution is delegated to a verification step that runs migrations only in a configured test environment.