Skip to content
cccskills
FreePublished on GitHub

prisma-migrate

Create a Prisma migration for a schema change against the local database. Use after editing prisma/schema.prisma.

The English summary is being prepared. Showing the original description.

howard36/probase20 stars(GitHub 20 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Migration name (from arguments, kebab-case; ask if missing): $ARGUMENTS

  1. Confirm prisma/schema.prisma has the intended change and nothing else (git diff prisma/schema.prisma).
  2. Generate and apply the migration against the local DB. The env wrapper is required; Prisma does not read .env.local on its own: 
    npm run local -- prisma migrate dev --name $ARGUMENTS
  3. Read the generated SQL under prisma/migrations/<timestamp>_<name>/migration.sql and check for destructive statements (DROP COLUMN, DROP TABLE, type changes on populated columns). Call these out explicitly in your reply.
  4. If the change affects seed data, update prisma/seed.mjs and re-run npm run local -- prisma db seed.
  5. Run /verify.

Remind the user in your reply: merging this PR to main runs prisma migrate deploy against production automatically. Never run migrations with npm run prod -- ... yourself.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

pr

Free

Commit the current changes on a new branch, push, and open a GitHub PR following this repo's conventions.

The English summary is being prepared. Showing the original description.

howard36/probase20Updated Sep 26, 2026

verify

Free

Verify a change is done by running lint, the Prettier check, the test suites, and a production build. Use after finishing any code change and before opening a PR.

The English summary is being prepared. Showing the original description.

howard36/probase20Updated Sep 26, 2026

See all skills by howard36

Report a problem with this skill