prisma-next-feedback
Draft Prisma Next Feedback for the Right Channel
Prisma Next feedback can be difficult to classify and prepare for public submission. This skill routes feedback and drafts complete, redacted reports.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "prisma-next-feedback" from https://skillstore.io/skills/prisma-prisma-next-feedback.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-next-feedback/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「prisma-next-feedback」を使用しています。 Migration planning exits successfully even when no migration is generated.
期待される結果:
Recommended channel: GitHub bug report. Draft title: bug(cli): migration plan exits successfully without a generated migration. The body requests version and reproduction details.
「prisma-next-feedback」を使用しています。 We need guidance for integrating an extension with an evolving Prisma Next API.
期待される結果:
Recommended channel: Prisma Discord. The draft opening message summarizes the integration, version, relevant API surface, and the specific compatibility question.
「prisma-next-feedback」を使用しています。 Prisma Next needs a first-party build plugin, and the current workaround is manual.
期待される結果:
Recommended channel: GitHub feature request. The draft explains the workflow gap, desired plugin behavior, current workaround, package scope, and expected impact.
セキュリティ監査
安全All 59 static findings are false positives caused by Markdown formatting, safe documentation links, secret-redaction guidance, or bounded workflow instructions. The skill requires explicit confirmation before GitHub submission and contains no prompt injection, credential access, or unsafe command interpolation.
リスク要因
⚙️ 外部コマンド (40)
🌐 ネットワークアクセス (9)
📁 ファイルシステムへのアクセス (1)
🔑 環境変数 (4)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/prisma-prisma-next-feedback/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/prisma-prisma-next-feedback?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/prisma-prisma-next-feedback?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-next-feedback/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/prisma-prisma-next-feedback.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-feedback security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prisma-prisma-next-feedback/audits/1BibTeX形式の引用
@techreport{prisma-prisma-prisma-next-feedback-2026,
author = {prisma},
title = {prisma-next-feedback security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prisma-prisma-next-feedback/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-feedback 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-feedback/audits/1"
identifiers:
- type: other
value: "skillstore:prisma-prisma-next-feedback:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Report a Reproducible Bug
Prepare a redacted issue with versions, steps, expected behavior, and actual behavior.
Request a Missing Capability
Turn a workflow gap into a focused feature request with scope, impact, and alternatives.
Ask the Prisma Team
Route an integration or design question to Discord with a concise opening message.
これらのプロンプトを試す
Decide whether this Prisma Next feedback belongs in GitHub, Discord, or another workflow skill: [describe the situation].
Draft a public-safe Prisma Next bug report from these details: [version, environment, command, output, steps, expected result, actual result].
Create a Prisma Next feature request for [missing capability]. Include the problem, proposed behavior, alternatives, affected packages, and current workaround.
Review [feedback details], separate bugs from feature requests, redact confidential content, draft each artifact, and request confirmation before any GitHub submission.
ベストプラクティス
- Provide exact package, Node, package manager, operating system, and database versions.
- Reduce bug reports to minimal steps and only the relevant contract excerpt.
- Review every public artifact and confirm it before submission.
回避
- Do not include credentials, customer data, or confidential schema names.
- Do not combine a bug and a feature request in one issue.
- Do not submit an issue automatically or without the user reviewing it.