data-migration-expert

Name: data-migration-expert
Availability: InStock
Author: Udecode

Validates SQL-backed data migrations and rollback safety against live production data.

240|75|Updated Jul 13, 2023

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

Ready to run

npx skills add https://github.com/udecode/plate-playground-template --skill data-migration-expert-udecode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-migration-expert
Source: https://github.com/udecode/plate-playground-template/tree/main/.codex/skills/data-migration-expert
Command: npx skills add https://github.com/udecode/plate-playground-template --skill data-migration-expert-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents data corruption by rigorously validating data migrations, backfills, and production data transformations against actual production reality, not just test fixtures.

Core Features & Use Cases

Production Data Validation: Verifies that migration mappings and transformations accurately reflect live data.
Bug Prevention: Catches common, dangerous migration bugs like swapped IDs, inverted values, and incomplete dual-writes.
Rollback Safety: Ensures concrete verification plans and rollback strategies are in place before deployment.
Use Case: When a database schema change involves renaming columns or converting enum values, this Skill will analyze the proposed migration against production data to ensure no data is lost or corrupted.

Quick Start

Use the data-migration-expert to review a pull request that modifies database schema and data.

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 data migrations against live production data?▼

Data migration validation requires explicit SQL queries to verify mapping logic and check for swapped or inverted values against actual production data, preventing data corruption before deployment.

What is the best way to prevent data corruption during a database schema change?▼

Preventing data corruption during a database schema change involves rigorously analyzing migration code and mapping logic against production reality, ensuring concrete verification plans exist before deployment.

How do I catch swapped IDs and inverted values during a data backfill?▼

Catching swapped IDs and inverted values during a data backfill requires verifying migration mappings against live production data using explicit SQL queries, ensuring transformations accurately reflect reality.

When do I need to verify dual-writes for a production data transformation?▼

You need to verify dual-writes for a production data transformation when modifying database schemas, ensuring incomplete dual-writes do not cause data loss during the migration process.

Does data migration validation work with test fixtures instead of production data?▼

Data migration validation focuses on verifying mappings against live production data rather than test fixtures, ensuring transformations accurately reflect reality and preventing dangerous migration bugs.