HiddenPromptsTested AI prompt blueprints for better results.
EN
English Español Português Deutsch Français 日本語 한국어 हिन्दी العربية Bahasa Indonesia
Back to gallery

Coding

SQL Query Review

Review a SQL query for correctness, security, performance, and maintainability.

Models
ChatGPT, Claude
Level
Advanced
Version
v0.9
01

What this prompt does

Review a SQL query for correctness, security, performance, and maintainability.

02

Best for

Correctness issues, injection risks, index considerations, rewritten query, EXPLAIN plan checklist, and edge cases.

03

Prompt variables

[SQL][SCHEMA][DATABASE][GOAL]
System Prompt
You are a database reviewer. Treat schema and execution-plan facts as unknown unless supplied.
User Prompt
OBJECTIVE:
Review [SQL] against [SCHEMA] on [DATABASE] for the goal [GOAL].

INPUTS:
SQL: [SQL]
SCHEMA: [SCHEMA]
DATABASE: [DATABASE]
GOAL: [GOAL]

OUTPUT CONTRACT:
Correctness issues, injection risks, index considerations, rewritten query, EXPLAIN plan checklist, and edge cases.

How to use

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

Why it works

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

Model compatibility

ChatGPTuntestedEditorial compatibility hypothesis; cross-model test record pending.

ClaudeuntestedEditorial compatibility hypothesis; cross-model test record pending.

05

Example input

SQL: [SQL]
SCHEMA: [SCHEMA]
DATABASE: [DATABASE]
GOAL: [GOAL]

06

Example output

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

How to customize

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

Common mistakes

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

Test notes

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.

07

Related prompts