Review the code the AI just wrote
A second model, a skeptical eye, and a list of what to fix before you ship.
Before merging or deploying anything an AI generated.code reviewqualitysecurity
Review this code as a senior engineer who assumes it was generated quickly and needs to be trusted in production. What the code is supposed to do: <one paragraph> The code: <paste> Where it runs: <browser / server / both>, and what data it touches: <user data, payments, files, none> Framework and constraints: <e.g. React + Supabase, must stay on the free tier> Review in this order, and rank findings by severity (critical / should fix / nice to have): 1. Correctness: does it do what I described? Any logic that is wrong or incomplete? Quote the lines. 2. Security and data: injection, exposed secrets, missing auth or permission checks, user input trusted without validation, data leaked to the client that shouldn't be. 3. Failure handling: what happens on a network error, a null, an empty list, a slow response, a double click. 4. Simplicity: code that does more than needed, duplicated logic, abstractions that hide rather than help. 5. Maintainability: naming, comments that explain "why", anything a teammate would trip on. For each finding: the line(s), what's wrong, why it matters, and the minimal fix. End with: the three things to fix before shipping, and one sentence on whether you would merge this as is. Do not rewrite the whole file. Do not praise it.
Replace every <placeholder> with your own details before you send it.
How to use it
- 1Use a different model or a fresh chat for the review. The one that wrote it will defend it.
- 2Ask it to rank by severity. Fix the top three; note the rest.
- 3Security and data handling issues are never 'later'.
Reviewed 2026-09-20
Good prompts are a skill. Proof of what you build is a career.
Join AgeBridge free: unlimited prompt generation, guided builds that turn into portfolio projects, and a community of AI builders who ship.
- Unlimited prompt generator
- Guided builds that become proof on your profile
- A public profile businesses can find
Related prompts
Vibe Coding
Tests that would have caught the last bug
Not 100% coverage. The five tests that protect what actually matters.
Write the small set of tests that would protect this code from the bugs it has actually had. The code: <paste the module or functions> What…
Open prompt
Vibe Coding
Refactor without changing behaviour
Same outputs, cleaner code, and a way to prove nothing moved.
Refactor this code without changing what it does. You are a disciplined engineer who makes small, provable changes. The code: <paste> What…
Open prompt
Vibe Coding
Write the spec before the first prompt
One page the AI can actually follow: screens, data, rules, and what's out.
You are a product engineer who writes specs that AI coding tools can follow without guessing. Help me write a one-page spec before I build…
Open prompt
Prompt text is written by AgeBridge and free to use. Results depend on the model and on the details you provide.