Skip to content

docs: update CONTRIBUTING.md to reflect current review workflow #309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
southpolesteve merged 1 commit into from
Mar 7, 2026
+6 −5
Merged

docs: update CONTRIBUTING.md to reflect current review workflow #309

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,20 +15,21 @@ We use [OpenCode](https://opencode.ai) with Claude Opus 4.6, set to max thinking

## AI code review

When you open a PR, tag one of our AI reviewers in a comment:
Every PR goes through AI code review. When you open a PR, a contributor with write access will request a review from **BigBonk** (Claude Opus 4.6, max thinking mode). External contributors can't trigger this directly.

- **`/bonk`** — AI code review using Claude Opus 4.6
- **`/bigbonk`** — Same model, max thinking mode. Use this for complex or large PRs.
Our process is to iterate on BigBonk's feedback until there are no unresolved comments. That doesn't mean you have to accept every suggestion verbatim, but we've found it to be very good at finding real problems and very useful for debugging this codebase. Expect multiple review rounds on larger PRs.

The reviewer will leave comments on your PR. You can respond to its comments and it will follow up.
**Our bias is towards merging.** This is a new project with known gaps, and we're trying to fill them as fast as possible. We want to get PRs in, not block them. If your contribution moves things forward, we'll work with you to get it landed.

At a maintainer's discretion, we may push BigBonk's recommended changes directly into your PR and merge it, or we may create a new PR based on your work. When we do this, we always try to preserve the original author credit. If that ever doesn't happen, please let us know and we'll fix it.

## Debugging

For browser-level debugging (verifying rendered output, client-side navigation, hydration behavior), we recommend [agent-browser](https://github.com/vercel-labs/agent-browser). Unit tests miss a lot of subtle browser issues. agent-browser has been effective at catching them throughout this project.

## What to work on

Check the [open issues](https://github.com/cloudflare/vinext/issues). Issues labeled `post-launch` are known gaps we're planning to address. If you're looking to contribute, those are a good place to start.
Check the [open issues](https://github.com/cloudflare/vinext/issues). If you're looking to contribute, those are a good place to start.

## Project structure

Expand Down
Loading