How it works
Start with a small workflow, protected secrets, explicit fork handling, and a dry run. Then observe the posted review before making it a required check.
For set up ai code review in github actions, use the published configuration and source repository as the product record. Keep the workflow small enough to inspect, and record any exception in the pull request rather than assuming a model result is final.
Limits to keep in view
Models, providers, and benchmark conditions change. Juror does not replace code ownership, test suites, static analysis, or a human decision to merge. Treat unknown cost and unevaluated compatibility as explicit unknowns.