prisma-next-debug
Diagnose Prisma Next Errors
Prisma Next failures expose detailed envelopes that can be difficult to route correctly. This skill maps codes, metadata, and symptoms to focused recovery steps.
安装前请停下并请求确认。
请审查安装计划，并在更改文件前获得用户明确同意。
使用我的智能体安装
将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。
Review the Skillstore skill "prisma-next-debug" from https://skillstore.io/skills/prisma-prisma-next-debug.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-next-debug/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“prisma-next-debug”。 A runtime envelope reports BUDGET.TIME_EXCEEDED with a strict latency limit.
预期结果:
Category: budget enforcement. Review query cost and the configured latency budget before increasing the threshold. Re-run the same workload after one controlled change.
正在使用“prisma-next-debug”。 A migration command returns PN-RUN-3000 and reports MIGRATION.HASH_MISMATCH in its metadata.
预期结果:
The outer code is a wrapper. The metadata identifies a migration hash mismatch. Re-emit the named migration, inspect the resulting diff, and verify state before applying changes.
正在使用“prisma-next-debug”。 A script prints query results but does not exit, and db.end is unavailable.
预期结果:
The Prisma Next client uses db.close for teardown. Close it after all queries complete. Do not close a shared client inside a request handler.
安全审计
高风险Static analysis misidentified Markdown inline-code formatting as executable shell syntax. The skill is documentation-only, but it recommends a command that can apply destructive database changes without explicit approval.
已确认安全问题 (1)
风险因素
⚙️ 外部命令 (50)
🌐 网络访问 (1)
📁 文件系统访问 (1)
🔑 环境变量 (1)
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/prisma-prisma-next-debug/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/prisma-prisma-next-debug?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/prisma-prisma-next-debug?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-next-debug/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/prisma-prisma-next-debug.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-debug security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prisma-prisma-next-debug/audits/1BibTeX 引用
@techreport{prisma-prisma-prisma-next-debug-2026,
author = {prisma},
title = {prisma-next-debug security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prisma-prisma-next-debug/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-debug 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-debug/audits/1"
identifiers:
- type: other
value: "skillstore:prisma-prisma-next-debug:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据 证据置信度: 中你能构建什么
Route a CLI failure
Identify the envelope code, severity, and metadata, then select the matching recovery path.
Recover a migration
Interpret migration wrappers, hash mismatches, drift, and marker diagnostics before choosing the next command.
Diagnose runtime behavior
Separate query, capability, budget, cancellation, and client lifecycle failures during incident response.
试试这些提示
Explain this Prisma Next error envelope and give the safest next step: [paste envelope].
Inspect this PN-RUN-3000 envelope, including meta.code, and identify the correct recovery workflow: [paste envelope].
Compare this migration status output with the contract hash and propose non-destructive verification steps: [paste output and context].
Create a prioritized recovery plan from these CLI, runtime, and SQL errors. Separate safe checks from commands requiring approval: [paste evidence].
最佳实践
- Provide the complete envelope, including code, severity, fix, metadata, and location.
- Use dry-run or verification commands before any operation that changes database state.
- Redact credentials and sensitive data from connection strings and diagnostic output.
避免
- Do not route only from the human summary or process exit code.
- Do not ignore meta.code when PN-RUN-3000 wraps the original failure.
- Do not bypass destructive-operation confirmation without explicit user approval.