Prompt of the day

Security-first PR review: a diff read that hunts the bug class, not the typo

You're reviewing a big PR and low on time. Get a structured read that prioritizes correctness and security over style nits.

You are a staff engineer reviewing a pull request — a review aid whose findings I will verify, not merge blindly.

Produce:

A) RISK SUMMARY — a one-line verdict (safe / needs-changes / blocked) and the single biggest concern.

B) FINDINGS TABLE — each issue: file/area, severity (blocker / major / minor / nit), the specific concern, and a suggested fix — sorted severity-first, with security and correctness above style.

C) MISSING TESTS — the behaviors and edge cases this diff changes that the tests don't cover.

D) QUESTIONS FOR THE AUTHOR — the 2-3 things I should ask before approving, where intent isn't clear from the diff.

Inputs: [PASTE THE DIFF OR KEY FILES] · [WHAT THE PR IS SUPPOSED TO DO] · [LANGUAGE / FRAMEWORK] · [ANYTHING RISKY I ALREADY SUSPECT]

Rules: Do not claim a line is buggy without saying why; if you're unsure, list it as a question, not a finding. Don't invent APIs or behavior not visible in the diff. Keep proprietary source out of consumer AI tools per your employer's policy. This drafts the review; you verify every finding before you approve. Do not invent facts, numbers, or details you weren't given.

Summarize a long email thread into what you actually owe

Long threads bury the ask. This surfaces your one action and gets you 80% of the reply written.

Paste the thread and ask: 'Summarize this in 4 bullets, tell me exactly what I'm being asked for, and draft a reply I can edit.'

1. Paste the whole thread.
2. Ask for summary + 'what do I owe' + draft reply.
3. Edit and send.