Code review
One review per push, written by the reviewers you define.
A code review is a kind: code_review file that names which pull requests to review and a list of reviewers, each a session with its own prompt, model, environment, and budget. Each push the file admits gets at most one review on the pull request, combining every reviewer's findings.
Review every push
Install the Ellipsis GitHub App on your repository, then commit this file to its default branch:
Open a pull request to see it work. Each push starts the reviewers whose paths match the new commits, and one review from ellipsis-dev[bot] lands with their comments. A reviewer only sees commits it has not reviewed before, and a comment on a line outside those commits is held back. A push with nothing new for any reviewer starts nothing. Every review, with each reviewer's comments and session, is listed under Code Review in the dashboard.
Configure a review
A file holds up to 8 reviewers, each with a unique name, and a repository holds one file. pull_requests takes the same filters as a pull request trigger. A reviewer takes the same environment, skills, and permissions blocks as an agent session; its budget takes only session.
A file in the .ellipsis repository reviews every repository its pull_requests.repositories filter admits; a file in a repository reviews that repository and wins over the organization file. A file that breaks a limit or does not parse fails the sync, keeps the last good version running, and shows the error in the Ellipsis config check on the pull request.
What happens when a reviewer fails
A review posts at most 30 comments per reviewer and 60 per review. A reviewer that returns more than 30 fails and contributes nothing; comments past 60 are kept with the review but not posted. When no reviewer has a comment, nothing is posted. A reviewer that fails or runs out of budget contributes nothing; the review still posts with the other reviewers' comments, and that reviewer covers the same commits again on the next push. When no reviewer finishes, nothing is posted and nothing is marked reviewed. When GitHub rejects the review, the review ends with status failed, nothing posts, and every reviewer covers the same commits again on the next push.
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 8 reviewers. Each runs as its own session on every push with a change in its range.
Spend limits every reviewer inherits.