Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jorgealves avatar

Database Migration Integrity Checker

  • 153 installs
  • 2 repo stars
  • Updated January 25, 2026
  • jorgealves/agent_skills

Verify database migrations apply cleanly, preserve schema invariants, and avoid data loss before releases by running structured integrity checks across environments.

About

database-migration-integrity-checker from jorgealves/agent_skills guides automated validation of SQL or ORM migrations, ensuring schemas stay consistent, constraints hold, and risky changes are flagged before deployment to staging or production.

  • Pre-deploy migration dry-run checks
  • Schema drift and constraint validation
  • Rollback and reversibility assessment
  • Seed and reference data integrity tests
  • CI-friendly migration verification reports

Database Migration Integrity Checker by the numbers

  • 153 all-time installs (skills.sh)
  • +8 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #261 of 911 Databases skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jorgealves/agent_skills --skill database-migration-integrity-checker

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs153
repo stars2
Last updatedJanuary 25, 2026
Repositoryjorgealves/agent_skills

What it does

Verify database migrations apply cleanly, preserve schema invariants, and avoid data loss before releases by running structured integrity checks across environments.

Files

SKILL.mdMarkdownGitHub ↗

Database Migration Integrity Checker

Purpose and Intent

The database-migration-integrity-checker is a safety net for your most critical asset: your data. It catches dangerous SQL operations that might pass a standard code review but could cause production outages or data loss.

When to Use

  • CI/CD Pipelines: Block deployments if a migration contains a high-risk operation without manual override.
  • Local Development: Run before committing a new migration to ensure it follows safe DDL practices.

When NOT to Use

  • Data Querying: This is for schema changes, not for auditing standard SELECT/INSERT queries.

Security and Data-Handling Considerations

  • Reads SQL files only; no database access required.
  • Safe for local use.

Related skills

Databasesdatabasespipelines

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.