ギャラリーに戻る

コーディング

PHP Debugging Investigation

Diagnose a PHP failure with ranked hypotheses, safe checks, and a minimal repair path.

モデル
DeepSeek, ChatGPT
レベル
上級
バージョン
v0.9

このプロンプトは現在英語で提供されています。画面は選択した言語のままです。

01

できること

Diagnose a PHP failure with ranked hypotheses, safe checks, and a minimal repair path.

02

最適な用途

Symptom summary, likely causes ranked by evidence, verification commands, minimal patch, regression checks, and rollback note.

03

プロンプト変数

[ERROR][CODE][ENVIRONMENT][EXPECTED_BEHAVIOR]
システムプロンプト
You are a senior PHP production engineer. Diagnose before changing code and do not invent runtime evidence.
ユーザープロンプト
OBJECTIVE:
Investigate [ERROR] in [CODE] running in [ENVIRONMENT]. Expected behavior: [EXPECTED_BEHAVIOR].

INPUTS:
ERROR: [ERROR]
CODE: [CODE]
ENVIRONMENT: [ENVIRONMENT]
EXPECTED_BEHAVIOR: [EXPECTED_BEHAVIOR]

OUTPUT CONTRACT:
Symptom summary, likely causes ranked by evidence, verification commands, minimal patch, regression checks, and rollback note.

使い方

Replace every variable with specific, non-sensitive information. Remove irrelevant sections and add one representative example when tone or classification matters.

効果の理由

The blueprint separates authority, task context, evidence limits, and the output contract so requirements can be checked independently.

モデル互換性

ChatGPTuntestedEditorial compatibility hypothesis; cross-model test record pending.

DeepSeekuntestedEditorial compatibility hypothesis; cross-model test record pending.

05

入力例

ERROR: [ERROR]
CODE: [CODE]
ENVIRONMENT: [ENVIRONMENT]
EXPECTED_BEHAVIOR: [EXPECTED_BEHAVIOR]

06

出力例

A structured deliverable following the listed output contract, with assumptions and missing evidence clearly marked.

カスタマイズ方法

Replace every variable with specific, non-sensitive information. Remove irrelevant sections and add one representative example when tone or classification matters.

よくある間違い

Do not paste secrets or personal data. Avoid contradictory constraints, unsupported facts, and using generated output without review.

テストメモ

Editorial blueprint awaiting recorded cross-model evaluation. It is visible for review but is not labeled as tested.

Why is this blueprint not marked as tested?

It has passed editorial structure review but does not yet have a published cross-model test record.