prisma-next-migration-review
Review Prisma Next Migrations Before Deployment
Deployment teams can misread migration state, refs, and divergent graph paths. This skill reviews the live origin, target destination, diagnostics, and pending operations.
ArrĂȘtez-vous et demandez confirmation avant lâinstallation.
Examinez le plan et obtenez le consentement explicite de lâutilisateur avant de modifier des fichiers.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "prisma-next-migration-review" from https://skillstore.io/skills/prisma-prisma-next-migration-review.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-next-migration-review/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « prisma-next-migration-review ». What will run when this branch deploys to staging?
RĂ©sultat attendu:
- Origin: the live staging database marker.
- Destination: the staging ref.
- Result: two pending migrations and no unreachable edges.
- Review required: one destructive operation must be approved before apply.
Utilisation de « prisma-next-migration-review ». Production ref and database marker do not match.
RĂ©sultat attendu:
The mismatch can indicate an out-of-band apply, a restored database, or divergent schema changes. Verify the live database before moving the ref.
Utilisation de « prisma-next-migration-review ». How should CI decide whether staging is deployable?
RĂ©sultat attendu:
Run migration status with the staging ref and database, inspect structured diagnostics, block warning severities, and preview operations before an approved apply.
Audit de sécurité
Risque élevéStatic findings are false positives caused by Markdown formatting, local examples, quoted database variables, and documentation links. One high-risk semantic issue remains: live migrations can execute without an explicit user confirmation requirement.
Préoccupations de sécurité confirmées (1)
Facteurs de risque
âïž Commandes externes (50)
đ AccĂšs au systĂšme de fichiers (2)
đ Variables dâenvironnement (5)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/prisma-prisma-next-migration-review/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/prisma-prisma-next-migration-review?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/prisma-prisma-next-migration-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-next-migration-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/prisma-prisma-next-migration-review.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
prisma. (2026). prisma-next-migration-review security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prisma-prisma-next-migration-review/audits/1Citation BibTeX
@techreport{prisma-prisma-prisma-next-migration-review-2026,
author = {prisma},
title = {prisma-next-migration-review security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prisma-prisma-next-migration-review/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-migration-review 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-migration-review/audits/1"
identifiers:
- type: other
value: "skillstore:prisma-prisma-next-migration-review:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Review a staging deployment
Identify the live staging marker, target ref, pending path, diagnostics, and destructive operations before deployment.
Resolve concurrent migration changes
Reassess a stale migration plan after another branch advances the shared graph head.
Create a migration CI gate
Check structured migration diagnostics and block deployment when warning conditions appear.
Essayez ces prompts
Explain the Prisma Next origin, destination, marker, and ref for my migration question. Identify what information is still missing.
Review what will run on staging. Use the staging database and staging ref, then summarize pending migrations, diagnostics, and destructive operations.
Investigate why the production ref and live database marker differ. Compare likely causes and recommend verification steps before changing either state.
Design a CI migration gate for staging. Parse structured diagnostics, fail on warnings, preview pending operations, and require approval before applying changes.
Bonnes pratiques
- Name the live database origin and intended destination ref before reviewing a deployment.
- Use structured diagnostics in CI instead of parsing human-readable summaries.
- Preview and summarize destructive operations, then obtain approval before applying live migrations.
Ăviter
- Do not treat a destination ref as a database connection selector.
- Do not move a ref only to silence a mismatch before investigating the cause.
- Do not rely on process exit status alone because warning diagnostics can exit successfully.