* add oxfmt formatter: config, scripts, CI, editor setup, docs * rebuild lockfile * fix: add Format to required checks list, remove dead ignore pattern * run fmt * add format to agents.md again
1.4 KiB
description, agent
| description | agent |
|---|---|
| Review a PR using the reviewer agent (different model) | reviewer |
Review pull request #$ARGUMENTS on cloudflare/vinext.
Steps
-
Read context: Run
gh pr view $ARGUMENTSto understand the PR — what issue it fixes, what the author claims it does. -
Read the diff: Run
gh pr diff $ARGUMENTSto see every change. -
Read full files: For each modified file, read the complete file (not just the diff) so you understand the surrounding code and can catch issues the diff alone won't reveal.
-
Check server parity: If any of these files were touched, check whether the others need matching changes:
packages/vinext/src/entries/app-rsc-entry.tspackages/vinext/src/server/dev-server.tspackages/vinext/src/server/prod-server.tspackages/vinext/src/cloudflare/worker-entry.ts
-
Check test coverage: Are the changes tested? Are edge cases covered? Run
gh pr diff $ARGUMENTSagain filtered to test files if needed. -
Post review: Use
gh pr review $ARGUMENTSwith your assessment:--approveif the PR is clean--request-changes --body "..."if there are blocking issues--comment --body "..."if there are only suggestions
For inline comments on specific files/lines, use:
gh api repos/cloudflare/vinext/pulls/$ARGUMENTS/comments -f body="..." -f path="..." -F line=N -f side="RIGHT"
Be thorough. This is the only review gate before merge.