Adjust code review to include incremental changes

[tnederlof]

• Extend the review workflow to run on PR synchronize events in addition to initial review triggers.
• Preserve the existing full-PR review behavior, while generating an incremental diff for follow-up reviews so the agent can focus on newly pushed changes (but still have access to the full diff for context).
• Pass PR action/SHA context into the review prompt
• Update the review skill guidance to prioritize incremental changes when available, using the full PR diff for broader context and valid inline comment placement.
• Regenerate the reusable workflow and consumer template so the example and shipped workflow stay aligned.

[vkodithala]

Is the implication here that we're gonna re-run a review whenever a contributor makes new commit? If so, this is probably lossy, since folks often make commits with in-flight changes - the true signal for what should be reviewed is probably a re-requested review.

I think what we probably want to do here is still only trigger the review-pr workflow for opened PRs and those with requested re-reviews, but include richer information about what's changed and/or previous reviews. Wdyt?

[tnederlof]

Yes, that sounds right @vkodithala, how can we set up this example action so it's easy for folks to request a rereview?

[tnederlof]

@vkodithala I took a stab at this direction, incorporating /oz-review as a trigger to do the re-review. I think it's common enough to include something like this right into our code review examples (versus only on the ready for review issue first time), but defer to you all on the best way to implement.

[vkodithala]

Thanks for the fixes!

Few nits, these changes mostly LGTM. If you have cycles, mind dropping review-pr into .github/workflows for a sample repo i.e. saleor and dogfooding that these changes work on re-review?

[vkodithala]

nit: Is there a reason we added fileComments.length > 0 here? Not important, but I don't actually think we need this conditional at all - the early return at :365-368 seems to handle.

Can probably just remove, but unimportant and defer to you.

[vkodithala]

I think we'll want to include context here that we also re-run PR review on comments that include "/oz-review".

[tnederlof]

So far it looks good, here is a test interaction I had on the Saleor repo: https://github.com/warpdotdev-demos/saleor/pull/83

[vkodithala]

This looks great, thanks so much for making these changes @tnederlof. Assuming you've tested this out, I'll cool with this going in!