db-change

Plan and execute safe database migrations with rollback.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/askaret/codex-skills --skill db-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-change
Source: https://github.com/askaret/codex-skills/tree/main/.agents/skills/db-change
Command: npx skills add https://github.com/askaret/codex-skills --skill db-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps plan, coordinate, and execute database migrations (schema and data) with safe rollouts and explicit rollback strategies, avoiding unintended changes to app logic.

Core Features & Use Cases

  • Backward-compatible migration strategy (expand → migrate → contract) to minimize downtime.
  • Idempotent, resumable data backfills with progress tracking and rollback readiness.
  • App-change coordination to ensure old and new schemas work together during rollout and verification.
  • Verification steps and runbooks to prepare production readiness.

Quick Start

Plan the migration, run it in staging, verify results, and prepare rollback documentation.

Frequently Asked Questions about db-change

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

FAQPage Schema
How do I plan a database migration with rollback for EF Core?

Plan an idempotent database migration by ensuring backfills are resumable with progress tracking and rollback readiness. This approach enforces backward-compatible steps and supports both online and offline rollout scenarios to safely apply schema and data changes.

What is the expand migrate contract pattern for schema migrations?

The expand migrate contract pattern is a backward-compatible database migration strategy that minimizes downtime. It coordinates application changes with schema updates so old and new application versions function together safely during online rollout and verification.

How do I run idempotent data backfills without locking tables?

Run idempotent data backfills by designing resumable scripts with progress tracking and rollback readiness. This minimizes database locking during online changes and ensures the backfill can safely resume if interrupted without corrupting data.

Can I coordinate application changes with database schema updates during rollout?

Yes, application changes can be coordinated with database schema updates during rollout. This ensures old and new schemas work together with the application, enforcing backward-compatible steps and providing verification runbooks for production readiness.

How do I verify database migration results in staging before production?

Verify database migration results in staging by following prepared verification steps and rollback runbooks. This process confirms backward-compatible schema and data changes apply correctly, ensuring production readiness before promoting the migration.