data-migration-expert

Validate database migrations and data backfills against production data.

5|Updated Oct 22, 2025

Search Tags:#rollback #database migration #data integrity #data validation #schema change #production data

Ready to run

npx skills add https://github.com/marchatton/agent-skills --skill data-migration-expert-marchatton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-migration-expert
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/05-review/data-migration-expert
Command: npx skills add https://github.com/marchatton/agent-skills --skill data-migration-expert-marchatton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents data corruption and ensures the safety and integrity of production data during database migrations, backfills, and schema changes.

Core Features & Use Cases

Production Data Validation: Verifies that migration mappings align with actual production data, not just fixtures.
Rollback Safety: Assesses and ensures that migration plans include safe rollback procedures.
Data Integrity Checks: Catches common migration bugs like swapped values, incomplete dual-writes, and orphaned associations.
Use Case: Reviewing a pull request that renames a critical user ID column, ensuring the mapping to the new column is correct and that rollback is possible if issues arise.

Quick Start

Use the data-migration-expert skill to review the attached database migration script for potential data integrity issues.

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 against production data to prevent corruption?▼

To validate database migrations, verify ID mappings and check for swapped values or orphaned associations against production reality, ensuring data integrity during schema changes. Explicit SQL queries are required to confirm production data verification.

How do I ensure rollback safety during a database schema change?▼

Rollback safety during a schema change requires a clear rollback plan that reverses data backfills and column renames. Assess migration scripts to verify that a safe rollback procedure is explicitly defined before deployment.

What data integrity issues should I check for when renaming a critical database column?▼

When renaming a database column, check for swapped values, incomplete dual-writes, and orphaned associations. Validate that the mapping to the new column aligns with actual production data rather than just test fixtures.

Do I need to provide explicit SQL queries for production data verification?▼

Yes, explicit SQL queries are required for production data verification. Providing these queries allows the migration analysis to check that ID mappings and data backfills align with actual production reality to prevent data corruption.

What is the best way to review a pull request for database backfill issues?▼

The best way to review a database backfill pull request is to validate the script against production data, checking for swapped values and verifying rollback safety. Ensure the plan includes explicit data verification queries and a rollback procedure.

Why does my data migration pass fixtures but corrupt production data?▼

Data migration passes fixtures but corrupts production data when ID mappings are not validated against production reality. Incomplete dual-writes and swapped values often go undetected without explicit SQL production data checks.