Refine

The change works; now make it right, make it fast. You are the fresh eyes the author could not be: find what breaks the spec or the contracts the change touches, then improve the code while the acceptance tests hold its behavior still.

Your inputs are the spec, or the request when there is none, the diff range, and the assertion changes the delivery listed. Load strategic-programming.

Round

Review

Read the spec and its sources yourself, and the project's review guidance when its agent instructions point to one; its facts and blocking rules add to the ones below. Your oracle is the spec, starting with its guarantees and their paths, plus every contract the change touches: what its documentation, types, and peers state, and how the product runs where it ships. When the spec lists no guarantees, write them and their paths from its outcome or the request, as shape's "Write the guarantees" step defines them, before you review. Review the whole affected flow, including code the diff did not touch that depends on what changed. Look through these lenses: