agentsclimarketplace

Prisma migrate

Skill K95M65/AI_ONBOARD/skills/prisma-migrate

Portable agent workflow framework for Codex, Claude Code, and OpenCode—shared project context, focused skills, independent review, and safe updates.

Install
npx -y skills add K95M65/AI_ONBOARD --skill prisma-migrate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Safely create and apply a Prisma schema migration, guarding against running against a non-local database. Use when changing prisma/schema.prisma or adding/altering database tables, columns, indexes, or relations.

SKILL.md

1.3 KB, 251 tokens by cl100k_base, as published. Nobody here has run it

Prisma migrate

When to use

Any change to schema.prisma — a new model, field, index, or relation. Never edit the database by hand and never hand-write migration SQL.

Steps

  1. Edit schema.prisma.
  2. Create the migration: 
    bash scripts/new-migration.sh <migration-name>
    • Generates the SQL and applies it to your local dev database via prisma migrate dev.
    • Refuses to run if DATABASE_URL looks non-local (staging/prod) unless you pass --force.
  3. Review the generated SQL under prisma/migrations/<timestamp>_<name>/ before committing.
  4. Commit schema.prisma and the new migration folder together.

Safety

  • The local-only guard is a safety net, not a substitute for judgment: migrating a shared or production database still requires explicit human confirmation.
  • Never delete or edit an already-applied migration — create a new one that carries the correction.
  • If migrate dev reports drift or wants to reset, stop and ask — a reset drops data.

What ships with it: 1 file

1.5 KB alongside SKILL.md, 1 of them executable

scripts/

Gives 0 of the 12 instructions most databases sql skills give in 251 tokens

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-07

  • Use parameterized queriesin 37 of 589, across 34 files
  • Use timestamptz for timestampsin 30 of 589, across 14 files
  • Index foreign keysin 29 of 589, across 18 files
  • Create indexes concurrentlyin 29 of 589, across 24 files
  • Use numeric type for moneyin 25 of 589, across 8 files
  • Use cursor pagination instead of offsetin 24 of 589, across 17 files
  • Select only required columnsin 24 of 589, across 20 files
  • Add indexes manually on foreign key columnsin 22 of 589, across 12 files
  • Normalize to third normal formin 19 of 589, across 10 files
  • Configure connection poolingin 19 of 589, across 17 files
  • Put equality columns before range columns in indexesin 18 of 589, across 10 files
  • Read individual rule files for detailed explanationsin 18 of 589, across 4 files

Said here and by no other author read

  • Edit schema.prisma for model changes
  • Commit schema and migration folder together
  • Require explicit human confirmation for shared databases
  • Stop and ask if a data reset is required

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.