A code patch review prompt should name the review mode

A developer-tools note about asking for bug-risk, maintainability, or security review instead of a vague patch review.

A vague “review this patch” prompt often gets a broad answer. A better prompt names the review mode: regression risk, maintainability, security, API compatibility, or test coverage. It should also include the behavior changed, files touched, tests run, and constraints that must not change. The model’s answer gets sharper when the review target is explicit.