Index of every page on this site: llms.txt
All skills
waynesutton avatar

/convex-migrations

@853b196
Run it yourself

Retired. Points to the skill that replaced convex-migrations in builder-skills 3.0. Use when /convex-migrations is invoked by name or the user asks where convex-migrations went.

Use this Skill: https://skilld.dev/gh/waynesutton/builder-skills/convex-migrations

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈49 tokens for metadata: the name and description. ≈144 when used: this file. ≈23 more on demand in 1 file.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈197 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

convex-migrations (retired)

This skill moved. Use convex-migrate (official Convex) and convex-migrate-rehearse (official Convex) instead. Tell the user this, then load the replacement if it is installed.

Install the replacement:

npx skills add convex/agent-skills --skill convex-migrate --skill convex-migrate-rehearse

Or set up Convex for your agent in one step: read and follow https://www.convex.dev/agent-setup.md.

Old content: https://github.com/waynesutton/builder-skills/tree/82d1ce2/skills/convex-migrations. Delete this folder after you switch.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill provides safe instructions and code patterns for performing database migrations on the Convex platform. It utilizes standard batching techniques, internal mutations for security, and a well-known community component for state management.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 853b196. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 2 weeks ago

README badge

README badge for waynesutton/builder-skills/convex-migrations

Implements safe schema migration patterns for Convex including adding fields with backfill, removing deprecated fields, renaming columns, adding indexes, and changing field types. Uses optional fields, batched mutations, and a migration tracker table to handle zero-downtime schema evolution without explicit migration files.

Generated from the current SKILL.md.

Does this skill handle zero-downtime migrations?
Yes. The skill covers zero-downtime patterns including adding optional fields first, backfilling data in batches via the scheduler, and only making fields required after backfill completes.
Can I rename fields with this skill?
Yes. The skill provides a pattern: add the new field as optional, backfill by copying data from the old field, update code to read from the new field with fallback, then remove the old field from the schema.
Does this work with Convex's schema system?
Yes. The skill is designed specifically for Convex, which has no explicit migration files—schema changes deploy instantly with `npx convex dev` and data is transformed via optional fields and backfill mutations.
How do I handle type conversions like string to number?
The skill includes a pattern: add a new field with the target type as optional, backfill with a mapping function to convert old values, update queries to read the new field with fallback, then remove the old field.
Can I track which migrations have already run?
Yes. The skill includes a migration runner pattern that stores migration metadata in a dedicated table with status tracking, allowing you to check if a migration has completed before running it again.

Generated from the current SKILL.md. These answers refresh after source changes.