Skills prisma-next-migrations
📦
prisma-next-migrations
Content revision r1 High Risk ⚙️ External commands📁 Filesystem access🔑 Env variables
Manage Prisma Next Database Migrations
Database changes can fail, drift, or lose data when migration steps are unclear. This skill guides Prisma Next planning, transforms, application, verification, and recovery.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "prisma-next-migrations" from https://skillstore.io/skills/prisma-prisma-next-migrations.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-next-migrations/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "prisma-next-migrations". I added an optional field on my local Postgres database. Which workflow should I use?
Expected outcome:
- Use the local database update path because the database has no shared migration history.
- Preview the operations before applying them.
- Switch to a formal migration before sharing or deploying the change.
Using "prisma-next-migrations". My generated migration contains a placeholder for a required column backfill.
Expected outcome:
- Open the generated migration source and replace every placeholder with a query-plan closure.
- Use a rowset check that identifies remaining invalid rows.
- Self-emit the migration package, inspect it, and apply it only after review.
Using "prisma-next-migrations". Migration application reports a hash mismatch.
Expected outcome:
The migration artifacts may be stale after source edits. Inspect the package, self-emit it, verify the changed files, then retry the migration.
Security Audit
High Riskv1 • 8/17/2026 Open versioned report
The Ruby backtick, path traversal, and reconnaissance alerts are scanner false positives caused by Markdown formatting, fixed imports, and documentation links. Database URL usage is confirmed because commands receive sensitive connection credentials. The skill also enables unprompted database mutation and execution of editable migration source, with no prompt injection or exfiltration intent found.
1
Files scanned
524
Lines analyzed
20
Review items
0
False positives ignored
Confirmed security concerns (2)
High
Unattended Destructive Database Migration
The skill directs users to apply pending migrations and states that migrate does not prompt. A mistaken target or missed destructive operation can cause production data loss.
The documented command applies database changes, and line 214 explicitly states that destructive operations run without a confirmation prompt.
High
Execution of Editable Migration Source
The skill instructs users to execute a repository migration file with Node. A malicious or compromised migration file can run arbitrary code with the agent's privileges.
The cited workflow directly executes an editable TypeScript migration file. Repository trust and source inspection are not enforced before execution.
Capability review items (20)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
Database connection strings
pnpm prisma-next db init --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next contract emit && pnpm prisma-next db update --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next migrate --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db verify --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db update --db $DATABASE_URL --dry-run
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db update --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db update --db $DATABASE_URL --json
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next migrate --show --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next migrate --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db schema --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db schema --db $DATABASE_URL --json > schema.json
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db verify --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db sign --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db schema --db $DATABASE_URL --json
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db verify --db $DATABASE_URL --json
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db verify --db $DATABASE_URL --json
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next db schema --db $DATABASE_URL --json
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next migrate --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
pnpm prisma-next migrate --db $DATABASE_URL
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
High
Database connection strings
- `pnpm prisma-next migration log --db $DATABASE_URL` — flat chronological table of applied migratio
This command expands $DATABASE_URL and passes the connection string to Prisma Next, granting access to a sensitive database endpoint. The use is intentional, but credential and target scope require protection.
Risk Factors
⚙️ External commands (50)
SKILL.md:12 SKILL.md:14 SKILL.md:16 SKILL.md:18 SKILL.md:25 SKILL.md:26 SKILL.md:30 SKILL.md:31 SKILL.md:32 SKILL.md:36 SKILL.md:37 SKILL.md:38 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:43 SKILL.md:44 SKILL.md:45 SKILL.md:46 SKILL.md:47 SKILL.md:48 SKILL.md:49 SKILL.md:50 SKILL.md:51 SKILL.md:52 SKILL.md:54 SKILL.md:56 SKILL.md:58 SKILL.md:60 SKILL.md:64 SKILL.md:65 SKILL.md:66 SKILL.md:72 SKILL.md:73 SKILL.md:74 SKILL.md:75 SKILL.md:76 SKILL.md:77 SKILL.md:78 SKILL.md:84 SKILL.md:85 SKILL.md:86 SKILL.md:87 SKILL.md:88 SKILL.md:90 SKILL.md:92 SKILL.md:94-100 SKILL.md:100-102 SKILL.md:102
📁 Filesystem access (5)
Audited by: codex
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/prisma-prisma-next-migrations/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/prisma-prisma-next-migrations?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/prisma-prisma-next-migrations?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-next-migrations/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/prisma-prisma-next-migrations.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
prisma. (2026). prisma-next-migrations security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prisma-prisma-next-migrations/audits/1BibTeX citation
@techreport{prisma-prisma-prisma-next-migrations-2026,
author = {prisma},
title = {prisma-next-migrations security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prisma-prisma-next-migrations/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "prisma-next-migrations security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "prisma"
date-released: "2026-08-17"
url: "https://skillstore.io/skills/prisma-prisma-next-migrations/audits/1"
identifiers:
- type: other
value: "skillstore:prisma-prisma-next-migrations:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
85
Maintainability
87
Content
65
Community
78
Spec Compliance
What You Can Build
Prepare a Local Schema Change
Choose a fast local update or create a reviewable migration package after changing a contract.
Review a Production Migration
Inspect planned operations, data transforms, and destructive changes before deployment.
Recover a Failed Deployment
Diagnose drift, marker mismatches, hash mismatches, or partial migration state.
Try These Prompts
Choose a Migration Path
I changed my Prisma Next contract for [change]. Should I use db update or migration plan? Explain the safest sequence.
Plan a Data Backfill
Help me plan a [Postgres or MongoDB] migration for [schema change]. Include the required backfill checks, transform steps, and verification.
Resolve a Migration Error
Diagnose [error code or message] in my Prisma Next migration. Explain likely causes, evidence to inspect, and recovery steps that preserve data.
Design a Production Rollout
Create a production rollout plan for [migration]. Address graph state, destructive operations, transaction behavior, backups, verification, rollback, and target database differences.
Best Practices
- Preview and inspect every migration before applying it to a shared database.
- Use one end-contract reference for every data transform query plan.
- Back up important data and confirm the database target before destructive operations.
Avoid
- Do not use direct database updates against shared or production environments.
- Do not edit canonical migration artifacts instead of the generated migration source.
- Do not run editable migration files from an untrusted repository.
Frequently Asked Questions
When should I use db update?
Use it for a private development database when you do not need replayable migration history.
When should I use migration plan?
Use it for shared branches, reviewed changes, production deployments, or changes requiring data transforms.
Why does a migration contain placeholders?
The planner detected required data work but cannot infer your business transformation logic.
How do I fix a migration hash mismatch?
Inspect the edited migration source, self-emit the package, review regenerated artifacts, and retry.
Does the skill support Postgres and MongoDB?
Yes. It explains their different imports, migration factories, markers, and transaction behavior.
Can I apply migrations without review?
No. Migration commands may run destructive operations, and formal migration application does not prompt for confirmation.