Code review & debugging21 categories
Security pass on this change
Anything touching auth, user input, file paths, or the database.
Review the code below for security problems only. Ignore style and performance. Check specifically: - Injection: SQL, command, template, path traversal - Authentication and authorisation: missing checks, checks that can be bypassed, IDOR - Input validation and its absence at trust boundaries - Secrets: hardcoded, logged, or sent where they shouldn't go - Data exposure: over-fetching, verbose errors, leaking internals to the client - Dependencies and version pins, if visible For each finding: the exact line, how it would be exploited concretely, and the fix. Rate severity. If you find nothing, say so rather than padding. Code:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Reviewing a change. Passes you run over a diff before it merges: correctness, security, concurrency, migrations.
Related prompts
Review this diff, correctness firstThe default review pass before you merge anything.Try to prove this code wrongWhen a review came back clean and you don't believe it.What tests am I missing?You wrote tests and want to know what you didn't think of.Is this migration safe to run?Before running a schema change against real data.Hunt for race conditionsAnything async, concurrent, or touching shared state.Is this thread-safe?Shared state, async work, or anything two callers can reach at once.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free