migrate

Migrate the schema + backfill data on a deployed Convex app (optional-first, then backfill, then require). TRIGGER on a live-schema-change/backfill request.

Jump to install

Repository: get-convex/convex-codex-plugin
Last source activity: July 7, 2026 at 16:41
Detected SKILL.md language: English
Stars: 5
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/get-convex/convex-codex-plugin --skill migrate

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name	migrate
description	Migrate the schema + backfill data on a deployed Convex app (optional-first, then backfill, then require). TRIGGER on a live-schema-change/backfill request.
license	Apache-2.0

Migrate the schema / data on a live app

Change a deployed schema without breaking existing data: stage the schema change, install @convex-dev/migrations, write a backfill that makes old rows valid, run it, and verify before tightening the validator.

Steps

Make the new field optional first (so deploy doesn't reject existing rows).
Install @convex-dev/migrations; write a migration that backfills/transforms existing rows.
Run the migration; verify all rows are valid.
Tighten the validator (make the field required) once the backfill is complete.

Rules

Never tighten a validator before the backfill completes — it rejects existing rows and breaks the live app.
Add new fields as optional first, migrate, then require.
Verify row counts before and after.

Back to search Back to installation

convex-expert

Convex backend rules — consult this whenever writing or editing any code inside a convex/ directory (schemas, queries, mutations, actions, HTTP endpoints, crons, file storage, auth, component installation). TRIGGER before touching convex/ functions, so the code uses the object-form syntax, validators, indexes, and component patterns that generic models get wrong.

2026-08-28

labs-quickstart

LABS — the FULL Convex quickstart experience: scaffold a running Next.js + shadcn app from one sentence with passkey (WebAuthn) sign-in and a live in-app Chef feedback panel pre-baked, build the idea live, then PUBLISH it to a public https://<app>.convex.app URL (with the user's confirmation before publishing). TRIGGER when the user runs $labs-quickstart, or asks for the full/labs quickstart, a published/public app, sign-in/passkeys, or the in-app feedback panel from scratch. For a plain local-only scaffold use $quickstart instead. SKIP when there's already a Convex project in the cwd.

2026-08-28

quickstart

Scaffold a running Next.js + shadcn Convex app from one sentence — convex dev + next dev already running — then build the idea live (runs locally). TRIGGER when the user wants to START a new Convex app from scratch — e.g. they ran $quickstart, said 'scaffold a new app', 'build me an app where users can ___', or 'new app'. SKIP when there's already a Convex project in the cwd.

2026-08-28

View all from this repository

name	migrate
description	Migrate the schema + backfill data on a deployed Convex app (optional-first, then backfill, then require). TRIGGER on a live-schema-change/backfill request.
license	Apache-2.0

Migrate the schema / data on a live app

Steps

Make the new field optional first (so deploy doesn't reject existing rows).
Install @convex-dev/migrations; write a migration that backfills/transforms existing rows.
Run the migration; verify all rows are valid.
Tighten the validator (make the field required) once the backfill is complete.

Rules

Never tighten a validator before the backfill completes — it rejects existing rows and breaks the live app.
Add new fields as optional first, migrate, then require.
Verify row counts before and after.

migrate

Source facts

Install options

Review the source files

Migrate the schema / data on a live app

Steps

Rules

More from this repository

Migrate the schema / data on a live app

Steps

Rules

More from this repository