Documentation

Juror documentation

Documentation is product truth: it preserves released identifiers and commands while making the surrounding task clear in each supported locale.

Read the docs How it works

Juror · Last reviewed: 2026-08-22

Direct answer

Documentation is product truth: it preserves released identifiers and commands while making the surrounding task clear in each supported locale.

01Install

02Configure

03Operate

Overview

What this covers

Documentation

Install Juror on a pull request

Add a pinned Juror workflow, set provider secrets, and inspect the first result.

→Documentation

Configure a Juror review

Set action inputs and repository configuration with safe, released defaults.

→Documentation

Choose presets and models

Select a released preset by review depth, speed, provider availability, and cost.

→Documentation

Use consensus mode

Configure the published-finding threshold and understand the false-positive trade-off.

→Documentation

Set review cost controls

Use receipts, targets, provider billing awareness, and coverage labels.

→Documentation

Set up post-merge browser QA

Configure an approved deployment, target journey, synthetic identity, and evidence rules.

→Documentation

Protect secrets and forked pull requests

Use event conditions and permissions that protect secrets when reviewing forked pull requests.

→Documentation

Benchmark Juror

Run the released benchmark command and record corpus, findings, cost, and limitations.

→Documentation

Troubleshoot Juror

Work through provider, setup, output, cost, and post-merge QA questions step by step.

→

How it works

Start from a pinned, least-privilege workflow.

The action reference uses a released commit SHA. Store provider keys in GitHub secrets and inspect the first review before you require it.

name: Juror review
on:
  pull_request:
    types: [opened, synchronize, reopened]

permissions:
  contents: read
  pull-requests: write

jobs:
  review:
    if: github.event.pull_request.head.repo.fork == false
    runs-on: ubuntu-latest
    steps:
      - uses: Juror-AI/juror@3eb0c88ce1931dd6227d554b2d9707ee4bca123f
        with:
          github-token: ${{ github.token }}
          preset: balanced
          cost-target-usd: "4.00"

How it works

Documentation is product truth: it preserves released identifiers and commands while making the surrounding task clear in each supported locale.

For juror documentation, 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.

Next task

Documentation