Code review schema reference
Complete code review examples and field reference.
A code review file has 5 top-level blocks: ellipsis, optional pull_requests, reviewers, optional output, and optional budget. Set ellipsis.kind to code_review. A repository holds one file at .ellipsis/code-review.yaml on its default branch; the .ellipsis repository holds the organization file. Unknown fields fail the sync. See Code review for what a review posts and what happens when a reviewer fails.
Review one organization
Committed to the .ellipsis repository, this reviews each push to a non-draft pull request by a human into main in api-repo or web-repo. pull_requests takes the same filters as a pull request trigger without on; a repository's own file wins over this one.
Approve when clean
A push with no blocking comment gets an approval that opens with the reviewer's summary; a push with one gets a request for changes carrying the comments. Without output, a pass posts nothing and a fail posts a comment.
Split reviewers by path
A push that changes db/migrations/ starts both reviewers; any other push starts only tests. The migrations reviewer runs in the api-environment environment with the skill installed, reads issues as well as contents and pull requests, and may spend $5 per run; tests inherits the $2 cap. A reviewer takes the same environment, skills, and permissions blocks as an agent session, except that permissions.github may only add read scopes. read_only reads every scope the GitHub App has.
Fields
Identifies the file.
Which pull requests to review. The same filters as a pull request trigger without on. Default every pull request by a human author.
1 to 64 reviewers. Each runs as its own session on every push with a change in its range.
What the review posts. A review passes when no reviewer returned a blocking comment and fails otherwise.
Spend limits every reviewer inherits.
See Models, the Environment schema reference, Permissions, and Budgets.