A second pair of eyes.
HOW TO ASK
"Review this code. Identify: security issues, missing error handling, and anything that would fail on unexpected input. Do not rewrite it."
That last constraint keeps the output as findings rather than a replacement you then have to review.
WHAT IT CATCHES
Missing validation Unhandled failure cases
Obvious security patterns: injection, weak checks, secrets in code
Inconsistency
WHAT IT MISSES
Anything requiring knowledge of your system Subtle logic errors Whether the code does what you actually wanted
WHAT IT IS GOOD FOR
A first pass before human review, not instead of it.
FOR SECURITY-SENSITIVE CODE
Review by a person who knows what they are doing.
Security failures are silent and pass every functional test.
THE USEFUL FOLLOW-UP
"What would an attacker try against this?"
Frequently surfaces something worth addressing.
