How it works
Juror runs in the pull-request workflow you already use. The workflow should be pinned, scoped to safe events, and explicit about provider credentials.
For multi-model ai code review, installed as a github action., 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.