Review a diff for production risk
Ask for a review that looks for what could break in a customer’s environment, not style nits.
Prompt · works with Any coding agent
Review the diff on this branch as if it ships to a customer's production environment tonight and I will not be on site tomorrow.
Ignore style and naming. Look only for:
- Behaviour changes a user would notice, intended or not.
- Data that could be lost, duplicated or written in a new shape.
- Assumptions about the environment: network access, file paths, environment variables, versions.
- Failure paths: what happens when a dependency is slow, down or returns something unexpected.
- How to roll this back, and whether that is safe after data has been written.
For each finding give the file and line, what would happen, and the smallest fix. If you find nothing serious, say that plainly instead of padding the list.