Skip to content
Log in

Review for the Bug, Not the Style

A code review that hunts correctness failures and states the exact input that breaks each one, instead of listing naming preferences.

0

Share this prompt

Free — no card needed

Create a free account

to open Review for the Bug, Not the Style — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryCodingForDevelopersTested onClaudeChatGPTGemini

Running it, start to finish

  1. Paste the diff along with what the code is meant to do and what calls it.
  2. Fix the findings that come with a concrete trigger first.
  3. Turn each trigger into a regression test before moving on.

What you get back

The output this produces, every time.

  • Works through six defect classes in order rather than reading top to bottom and commenting as it goes.
  • Requires a concrete triggering input for every finding, and marks the ones it could not produce as speculative.
  • Reports which classes came back clean, so a short review is distinguishable from a shallow one.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Describe the calling context. Most real defects are contract mismatches between caller and callee. Reviewing a function in isolation finds only the shallow half.
  • Read the SPECULATIVE section last and lightly. It is where false positives concentrate. The findings with real triggers are the ones worth acting on.
  • Check the Clean list. against your own sense of the code. If it claims concurrency is clean and you know there are two writers, your context description was incomplete.

More Coding prompts

All Coding

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.