database-migrations

What This Skill Does

The database-migrations skill provides OpenClaw agents with expert-level knowledge of schema evolution and data handling in production environments. It focuses on zero-downtime deployment patterns, ensuring that database schema changes do not cause outages or performance degradation. By leveraging industry-standard strategies like Expand-Contract and Additive-Only changes, the skill helps developers manage complex database lifecycle tasks, from simple column additions to high-stakes table refactoring. It also assists in selecting the appropriate migration tool based on your project's stack (e.g., Prisma, Drizzle, Alembic, or Flyway) and helps draft effective rollback strategies for risk mitigation.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/wpank/database-migrations

Use Cases

• Planning schema changes: Determine whether a requested change requires a simple additive migration or a multi-phase Expand-Contract approach.
• Performance optimization: Identify dangerous DDL operations (like adding a non-concurrent index) and provide safer alternatives.
• Rollback planning: Design and document the necessary rollback procedures for sensitive data migrations.
• Tooling evaluation: Compare migration tools like Atlas or Flyway against your existing framework to ensure better CI/CD integration.
• Production reviews: Audit pending migration files for common anti-patterns like long-running transactions on primary keys.

Example Prompts

1. "I need to rename a column in a production table with 50 million rows. How do I do this without downtime or locking the table?"
2. "Draft a three-step migration plan for changing a user_id column from integer to UUID, including the dual-write logic."
3. "Evaluate these two migration strategies: adding a NOT NULL column with a default value versus using a nullable column and backfilling later. Which is safer?"

Tips & Limitations

Always prefer declarative tools when your schema complexity allows, as they reduce the likelihood of human error during development. Remember that this skill provides structural and procedural guidance—it does not execute SQL directly against your database. Always test your generated migrations in a staging environment that mirrors production data volume to verify performance impacts. If you are dealing with massive datasets, favor lazy migration patterns over bulk updates to keep replication lag within acceptable limits.