vinext is a Vite plugin that provides the Next.js API surface so Next.js applications can run on Vite, with Cloudflare Workers as its primary deployment target. Developers use it to develop, build, and deploy applications using features such as routing, React Server Components, Server Actions, middleware, and static generation. The catalogue entries support migration and use of vinext.
Borrowing it
Nothing to install: this file belongs to cloudflare/vinext. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cloudflare/vinext/main/.opencode/commands/review-pr.mdgit clone --depth 1 https://github.com/cloudflare/vinextWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/cloudflare/vinext/review-pr)<a href="https://agentmods.dev/commands/cloudflare/vinext/review-pr"><img src="https://agentmods.dev/badge/commands/cloudflare/vinext/review-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/cloudflare/vinext/review-pr"><img src="https://agentmods.dev/badge/commands/cloudflare/vinext/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00011 | $0.00383 |
| Opus 5.5 | $0.00004 | $0.00153 |
| Sonnet 5.5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
review-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
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.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 36 lines · 11 tokens per session scan A a593319789f4
review-pr is a command published in the GitHub repository cloudflare/vinext (9,263 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 383 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
release-tag
Create and push a version tag after a release PR has been merged.