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.
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-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.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-debug ». A runtime envelope reports BUDGET.TIME_EXCEEDED with a strict latency limit.
RĂ©sultat attendu:
Category: budget enforcement. Review query cost and the configured latency budget before increasing the threshold. Re-run the same workload after one controlled change.
Utilisation de « prisma-next-debug ». A migration command returns PN-RUN-3000 and reports MIGRATION.HASH_MISMATCH in its metadata.
RĂ©sultat attendu:
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.
Utilisation de « prisma-next-debug ». A script prints query results but does not exit, and db.end is unavailable.
RĂ©sultat attendu:
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.
Audit de sécurité
Risque élevé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.
Préoccupations de sécurité confirmées (1)
Facteurs de risque
âïž Commandes externes (50)
đ AccĂšs rĂ©seau (1)
đ AccĂšs au systĂšme de fichiers (1)
đ Variables dâenvironnement (1)
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-debug/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/prisma-prisma-next-debug?utm_source=security_passport_badge)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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation 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/1Citation BibTeX
@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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces prompts
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].
Bonnes pratiques
- 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.
Ăviter
- 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.