qa-db-migrations
Database migration testing for Flyway, Liquibase and Atlas: classify every schema change by risk and review blast radius and locking before it ships. Sorts DDL and DML into an eight-category operation taxonomy. A review agent (migration-blast-radius-reviewer) covers blast radius plus DDL performance: CONCURRENTLY index builds, ACCESS EXCLUSIVE rewrites, post-migration ANALYZE, and lock-time estimates.
/plugin install qa-db-migrations@testland-qaFirst time? Add the marketplace with /plugin marketplace add testland/qa
- Category
- Backend & distributed systems
- Version
v1.3.6- Contents
- 4 skills · 1 agent
- Part of
- qa-role-backend
Skills4
atlas-migrationsUse when a team wants declarative, Terraform-style database schema management or migration linting beyond Flyway and Liquibase: Atlas schema apply, migrate diff against a dev database, migrate lint for destructive or locking changes, and migrate hash, across a dozen databases.skillflyway-migrationsUse whenever a schema is managed with Flyway: versioned, repeatable and undo migration files, migrate, info, validate, baseline and repair, the schema history table, migration ordering questions, and CI gates on schema changes, via CLI, Maven, Gradle or Docker.skillliquibase-migrationsUse whenever a schema is managed with Liquibase: changelogs and changesets in XML, YAML, JSON or SQL, update, status, rollback and tag, preconditions, contexts and labels, and the changelog lock tables, for portable migrations across databases with fine rollback control.skillmigration-operation-taxonomyUse whenever someone asks if a database migration is safe to run in production: rename or drop a column, add NOT NULL or a default, add an index or foreign key, change a type on a large PostgreSQL or MySQL table.skill
Agents1
About qa-db-migrations
Database migration testing. Three per-tool skill wrappers covering the mainstream database migration ecosystem (Flyway, Liquibase, Atlas), the operation taxonomy they share, plus an adversarial reviewer agent that classifies operations against an 8-category taxonomy, runs a DDL performance review, and refuses to approve production-unsafe patterns.
Anchored on the ISO 25010 portability characteristic. Universal need: every team that ships schema changes.