db-migrate

Detect and apply database schema changes across environments via GitHub workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sandwichlab-ai/sandwichlab-skills --skill db-migrate-sandwichlab-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-migrate
Source: https://github.com/sandwichlab-ai/sandwichlab-skills/tree/main/skills/db-migrate
Command: npx skills add https://github.com/sandwichlab-ai/sandwichlab-skills --skill db-migrate-sandwichlab-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the detection and application of database schema changes across services and environments, reducing manual migration work and risk.

Core Features & Use Cases

  • Diff: detect schema differences between environments or services.
  • Exec: run migrations based on a documented change window.
  • Status: monitor migration progress and results across dev, preprod, and prod.
  • Use Case: coordinate cross-service migrations for shared schemas.

Quick Start

Diff the schema for your app and environment, then apply the corresponding migration and verify the result before promotion.

Frequently Asked Questions about db-migrate

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

FAQPage Schema
How do I automate database schema migrations across multiple environments?

Database schema migrations can be automated across dev, preprod, and prod using a GitHub-based workflow. This process validates changes and manages environment scope to reduce manual migration work and risk.

Can I detect schema differences between services before running a migration?

Yes, you can detect schema differences between environments or services using a diff operation. Comparing schemas helps coordinate cross-service migrations for shared databases before applying changes.

How do I monitor database migration progress across dev, preprod, and prod?

You can monitor database migration progress and results across dev, preprod, and prod using a status operation. This provides visibility into workflow-driven migrations executed within a documented change window.

Does this database migration workflow work with GitHub Actions?

Yes, this database migration workflow operates using GitHub-based workflows and GitHub Actions. It relies on this workflow-driven process to validate schema changes and manage environment scope before promotion.

What is the best way to coordinate cross-service migrations for shared schemas?

The best way to coordinate cross-service migrations for shared schemas is using a workflow-driven process to validate changes. You can diff the schema, run migrations within a documented change window, and verify results before promotion.