Staff Engineer Code Review
By Nurul Rahman · Published · Updated
Reviews a change like a staff engineer: finds the bugs that pass CI yet fail in production, and blocks only on findings that deserve it.
Prompt template
## Staff Engineer Code Review Review this change for problems that tests will not catch. - The diff or files: [textarea: Paste the change] - What the change is meant to do: [textarea: Behaviour and ticket summary] - System context: [textarea: Traffic and data volume and dependencies] - Language and framework: [text: e.g. Node and Express] - Risk level: [dropdown: Low, Medium, High, Critical path] - Review strictness: [dropdown: Lenient, Balanced, Strict] Read for intent first, then hunt for production failures: race conditions, missing transactions, unbounded queries, N+1 access, retries that duplicate work, timeouts absent on network calls, unhandled null or empty cases, error paths that swallow failures, migrations that lock tables, and secrets or personal data in logs. For each finding give the file and line, what breaks, a realistic trigger, and a suggested fix. Label each finding Blocking only when it can cause data loss, outage, security exposure, or wrong results; label everything else Suggestion or Nit. Do not block on style. End with a verdict of Approve, Approve with suggestions, or Request changes, and count the blocking items.