Menu
Run prisma migrate dev, regenerate client to the correct output path, and verify import paths
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.
Based on SOC occupation classification
Implement a numbered testing strategy phase from docs/testing_strategy_phases/phase_$ARGUMENTS_*.md step by step
Implement a numbered phase from docs/phases/phase-$ARGUMENTS.md step by step
Review changed code for correctness, security, and project conventions. Invoke this skill automatically whenever a complete unit of work is done — a full implementation phase, a complete feature (repository + service + route + component all connected), or just before creating a PR. Do NOT invoke after editing a single file or mid-way through a feature. If the user says "done", "finished", "phase complete", "ready to commit", or similar, trigger this review immediately.
Scaffold a Prisma-backed repository for a given Prisma model
Scaffold a service class for a given domain following project conventions
Final pre-commit check: run type-check (npx tsc --noEmit), lint (npm run lint), and tests (npm test)
| name | db-migrate |
| description | Run prisma migrate dev, regenerate client to the correct output path, and verify import paths |
| disable-model-invocation | true |
Run a Prisma migration, regenerate the client, and verify import paths.
npx prisma validate
Fix any errors before proceeding.
npx prisma migrate dev --name <describe-the-change>
Use a descriptive snake_case name (e.g., add-invoice-line-items).
migrate dev uses DIRECT_URL from .env.local (bypasses PgBouncer — already configured in schema.prisma's directUrl field). If it fails with "cannot connect", check that DIRECT_URL is set and points to port 5432.
migrate dev runs prisma generate automatically, but confirm explicitly:
npx prisma generate
ls src/app/generated/prisma/
You should see client/, index.d.ts, etc. If the directory is empty, the output path in schema.prisma is wrong.
grep -rn "from '@prisma/client'" src/ tests/
grep -rn 'from "@prisma/client"' src/ tests/
Any hits must be changed to @/app/generated/prisma/client.
npx tsc --noEmit
Type errors referencing @prisma/client or missing Prisma types indicate wrong imports or a failed prisma generate.
ls prisma/migrations/
Review the new migration SQL briefly — especially for destructive operations (DROP COLUMN, etc.).
prisma migrate dev is for local development only. Production uses prisma migrate deploy in CI — never run it locally.