backend-migration-writer

Write reversible database migrations with up/down scripts and data backfills.

6|Updated Apr 24, 2026

Search Tags:#rollback #database #migrations #backend #sql #idempotent #backfill

Ready to run

npx skills add https://github.com/lookatitude/guild --skill backend-migration-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-migration-writer
Source: https://github.com/lookatitude/guild/tree/main/skills/specialists/backend-migration-writer
Command: npx skills add https://github.com/lookatitude/guild --skill backend-migration-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables writing safe, reversible database migrations with explicit up and down scripts, paired data backfills, and a rollback strategy, so production schema changes can be deployed with confidence.

Core Features & Use Cases

Up/Down migration scripts, data backfills, and rollback strategies for safe schema changes.
Idempotent, lock-budget aware migrations that minimize disruption on hot tables and support zero-downtime deploys.
Clear deployment planning and traceability for CI/CD coordination.

Quick Start

Draft a migration plan to add a new nullable column with a corresponding backfill and a rollback path.

Frequently Asked Questions about backend-migration-writer

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

FAQPage Schema

How do I write reversible database migrations with up and down scripts?▼

Reversible database migrations require explicit up and down scripts paired with a rollback strategy. This approach generates idempotent DDL and batched data backfills to ensure production schema changes can be safely deployed and undone.

What is the best way to backfill data during online schema migrations?▼

Backfilling data during online schema migrations requires batched updates to minimize lock duration on hot tables. This ensures zero-downtime deploys by applying data backfills alongside idempotent DDL changes with an explicit rollback path.

How do database migrations handle rollback strategies for production deploys?▼

Rollback strategies for production database migrations rely on documented deploy orders and explicit down scripts. This ensures that schema changes and data backfills can be safely reversed if an issue arises during a production deploy.

Can I perform zero-downtime migrations on hot tables without locking issues?▼

Zero-downtime migrations on hot tables require lock-budget aware execution and idempotent DDL. By using batched backfills and minimal lock duration strategies, production schema changes avoid disruption and maintain availability.

Why do database migrations need to be idempotent for CI/CD coordination?▼

Database migrations need to be idempotent to ensure repeated executions do not cause errors during CI/CD coordination. This provides clear deployment planning and traceability, allowing safe retries of schema changes and data backfills across environments.

When should I use batched data backfills instead of direct schema updates?▼

Batched data backfills are necessary when applying schema changes to hot tables in production. They minimize lock duration and ensure online migrations remain safe, allowing data to be populated gradually without disrupting zero-downtime deploys.