GalleryCoding & Technical
Review a code change before it merges
When you want a second pair of eyes on a diff or pull request, for the bugs and risks a quick read would miss.
Updated
Review the code change below. It [Purpose].
Look for, in this order:
1. Bugs: wrong logic, unhandled cases, race conditions, off-by-one errors.
2. Security: injection, missing authorization, leaked secrets, unchecked input.
3. Performance: needless work in loops, extra queries, memory that keeps growing.
4. Clarity, only where it would cause mistakes later.
For each finding, give the file and line, what's wrong, why it matters, and a fix, and rate it High, Medium or Low, highest first. Skip formatting a linter would catch. If you find nothing serious, say so plainly instead of inventing issues.
Diff:
Something wrong with this prompt? Tell us at support@softifacts.com