技能 prisma-next-migration-review
📦
prisma-next-migration-review
內容修訂 r1 高風險 ⚙️ 外部命令📁 檔案系統存取🔑 環境變數
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.
支援: Claude Codex Code(CC)
安裝前請停止並請求確認。
請審查安裝計畫，並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
智能體請求
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.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「prisma-next-migration-review」。 What will run when this branch deploys to staging?
預期結果:
- 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.
正在使用「prisma-next-migration-review」。 Production ref and database marker do not match.
預期結果:
The mismatch can indicate an out-of-band apply, a restored database, or divergent schema changes. Verify the live database before moving the ref.
正在使用「prisma-next-migration-review」。 How should CI decide whether staging is deployable?
預期結果:
Run migration status with the staging ref and database, inspect structured diagnostics, block warning severities, and preview operations before an approved apply.
安全審計
高風險v1 • 2026/8/17 開啟版本化報告
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.
1
已掃描檔案
229
分析行數
0
複核項目
0
已忽略的誤報
已確認的安全問題 (1)
高
Database migrations can run without explicit user confirmation
The skill provides live staging and production apply commands, while noting that migrate has no destructive-operation prompt. An agent could apply destructive planned changes without explicit approval.
The apply commands and missing confirmation behavior are explicitly documented. The skill warns about review but does not require user approval before mutation.
風險因素
⚙️ 外部命令 (50)
SKILL.md:17 SKILL.md:18 SKILL.md:24 SKILL.md:25 SKILL.md:26 SKILL.md:34 SKILL.md:42 SKILL.md:43 SKILL.md:45 SKILL.md:49 SKILL.md:51 SKILL.md:53 SKILL.md:55 SKILL.md:59 SKILL.md:63 SKILL.md:64 SKILL.md:65 SKILL.md:66 SKILL.md:67 SKILL.md:68 SKILL.md:69 SKILL.md:70 SKILL.md:74 SKILL.md:76 SKILL.md:77 SKILL.md:79 SKILL.md:83 SKILL.md:87 SKILL.md:88 SKILL.md:89 SKILL.md:90 SKILL.md:92 SKILL.md:98 SKILL.md:100-102 SKILL.md:102-107 SKILL.md:107-108 SKILL.md:108 SKILL.md:111-113 SKILL.md:113-115 SKILL.md:115 SKILL.md:119-125 SKILL.md:125 SKILL.md:127-128 SKILL.md:128-132 SKILL.md:132 SKILL.md:134 SKILL.md:140-143 SKILL.md:143 SKILL.md:146-148 SKILL.md:148
📁 檔案系統存取 (2)
🔑 環境變數 (5)
審計單位: codex
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/prisma-prisma-next-migration-review/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/prisma-prisma-next-migration-review?utm_source=security_passport_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>嵌入卡片
<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>學術引用 (APA · BibTeX · CFF)
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/1BibTeX 引用
@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"
Skillstore 評分
評分依據 證據置信度: 中 55
架構
85
可維護性
87
內容
65
社群
83
規範符合度
你可以打造什麼
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.
試試這些提示
Explain migration state
Explain the Prisma Next origin, destination, marker, and ref for my migration question. Identify what information is still missing.
Review pending staging migrations
Review what will run on staging. Use the staging database and staging ref, then summarize pending migrations, diagnostics, and destructive operations.
Investigate a ref mismatch
Investigate why the production ref and live database marker differ. Compare likely causes and recommend verification steps before changing either state.
Design a guarded CI workflow
Design a CI migration gate for staging. Parse structured diagnostics, fail on warnings, preview pending operations, and require approval before applying changes.
最佳實務
- 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.
避免
- 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.
常見問題
Does this skill create migrations?
No. It reviews migration state and deployment paths. Use a migration-authoring workflow to create or re-plan migrations.
Why is a database connection needed?
The live database marker defines the origin. Offline review cannot determine which migrations are already applied.
What does a ref represent?
A ref is a named pointer to a contract hash and optional invariants. It does not select a database.
How are concurrent migrations resolved?
Rebase onto the new graph head, then repeat the edit, plan, and apply workflow. Port custom data transformations manually.
Can CI rely on the command exit code?
No. Some warning diagnostics exit successfully. CI should parse structured diagnostics and fail according to severity and code.
Does migrate ask before destructive changes?
No. Review status and operation counts first, then require explicit approval before running migrate against a live environment.