payload-migrations

Generate, verify, and apply Payload CMS schema migrations to Postgres databases.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill payload-migrations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: payload-migrations
Source: https://github.com/fsolla/teqo/tree/main/.cursor/skills/payload-migrations
Command: npx skills add https://github.com/fsolla/teqo --skill payload-migrations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of managing database schema changes in a production-grade Payload CMS environment, preventing drift and ensuring safe, idempotent deployments.

Core Features & Use Cases

  • Schema Versioning: Provides a structured workflow for creating, applying, and tracking database migrations.
  • Data Reconciliation: Supports hand-written migrations for complex data backfills or type changes that automated diffs cannot handle.
  • Use Case: When adding a new field to a collection or renaming a column, use this skill to generate the migration file, verify the SQL, and ensure the change is safely applied during the next production deployment.

Quick Start

Use the payload-migrations skill to generate a new migration file after you have updated your collection configuration.

Frequently Asked Questions about payload-migrations

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

FAQPage Schema
How do I manage Payload CMS database schema migrations for Postgres?

Manage Payload CMS database schema migrations by generating, verifying, and applying SQL changes to Postgres databases. The process provides a structured workflow for creating, applying, and tracking database schema versions to prevent drift.

What is the best way to handle complex data backfills in a Payload CMS migration?

Complex data backfills in a Payload CMS migration are handled through hand-written migrations. This approach supports complex data reconciliation and type changes that automated schema diffs cannot safely process.

How do I generate a migration file after updating a collection configuration in Payload CMS?

Generate a migration file after updating your collection configuration by using the migration workflow. It creates the necessary SQL changes, verifies them, and ensures the changes are safely applied during the next production deployment.

Does the payload-migrations skill work with Vercel and Neon production environments?

Yes, the migration process supports production environments using Vercel and Neon. It enforces strict adherence to the existing migration chain and baseline constraints to ensure safe, idempotent deployments on Postgres databases.

Why do I need to follow strict migration chain constraints in Payload CMS?

Strict adherence to the existing migration chain and baseline constraints is required to prevent schema drift. Following these constraints ensures that database schema changes remain safe and idempotent across production environments.

Can I use automated schema diffs for every database migration in Payload CMS?

Automated schema diffs cannot handle every database migration scenario. You need hand-written migrations for complex data backfills or type changes, ensuring accurate data reconciliation when automated tools fall short.