data-migration-expert

Validate database migrations for ID mappings and rollback safety.

3|1|Updated Jan 15, 2026

Search Tags:#rollback #database #data integrity #migration #PR review #ID mappings

Ready to run

npx skills add https://github.com/i3ringit/antigravity-cortex --skill data-migration-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-migration-expert
Source: https://github.com/i3ringit/antigravity-cortex/tree/main/.agent/skills/data-migration-expert
Command: npx skills add https://github.com/i3ringit/antigravity-cortex --skill data-migration-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this agent to validate database migrations by verifying ID mappings and data integrity, ensuring production reality is preserved during schema changes.

Core Features & Use Cases

Migration validation: Check ID mappings and data consistency across environments.
Integrity auditing: Ensure migrated data aligns with production reality and rollback plans.
Use Case: When a PR touches migrations or data backfills, run this agent to verify mappings and prepare rollback evidence.

Quick Start

Use the data-migration-expert on a PR involving database migrations to validate ID mappings and verify rollback safety.

Frequently Asked Questions about data-migration-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate database migrations for ID mapping errors before deploying?▼

Validate database migrations by verifying ID mappings match across source and target tables, checking for swapped or missing values. Use query-based post-deploy validation to confirm correctness and ensure rollback safety before production deployment.

What should I check in a PR that modifies database migrations?▼

Review database migration PRs for correct ID mappings, data integrity during transforms, dual-write safety, and explicit rollback plans. Verify the migration preserves production data consistency and includes evidence that rollback is safe and reversible.

How do I ensure data backfills maintain referential integrity?▼

Data backfills maintain referential integrity by validating ID mappings between related tables, confirming no orphaned or swapped records exist. Query production after deployment to prove migrated data aligns with expected relationships and rollback procedures.

What's the best way to plan rollback for a schema migration?▼

Plan migration rollback by documenting explicit rollback steps, testing reverse transformations on non-production data, and preparing query-based validation that proves data can safely revert. Validate dual-write strategies to minimize data loss during rollback execution.

Can I use this for validating data transforms that swap column values?▼

Yes. This validation focuses on detecting value swaps and incorrect ID mappings in data transforms. It verifies that swapped values are intentional, mappings are bidirectional where required, and production data remains consistent after the transform.

What prerequisites do I need before running migration validation?▼

Before validation, you need access to the migration code, production and staging database schemas, and sample data or queries that expose ID relationships. Documentation of expected mappings and rollback procedures strengthens validation accuracy.