path:line. It never approves and never merges. A person does both.
This is autopilot-pr-review, one of the Autopilot built-ins. It declares its own GitHub triggers, so you turn it on rather than write it, and it needs no machine.
Before you begin
- The
reliantCLI, v1.21 or later, signed in (Sign in and tokens), andghfor the GitHub side. - The Reliant GitHub App installed on the repository, and push access to it on your own account (GitHub integration).
- In an organization: an organization AI account that can run the reviewer’s model (the
powerfultag by default). See What this does not do.
1
Create a project for the repository
Run this in a clone of the repository.
project create is idempotent: if the path already has a project, it prints that project’s ID.terminal
2
Turn on PR review
--param repos= names the repositories to review. Nothing outside that list is ever reviewed. --no-machine is right because the reviewer reads code through GitHub only.terminal
reliant-labs[bot]), so it can request changes on your own pull requests too. --param 'review_guidance=...' gives the reviewer context; every setting is in Autopilot settings. In the app, this is Workflows → Library → Autopilot · PR review → Set up.3
Open a pull request
This test change has two bugs on purpose: the loop reads one element past the end, and an empty slice divides by zero.
stats/stats.go
terminal
launched means the review started. Follow it with reliant workflow follow <chat> or under Workflows → Runs.4
Read the review
terminal
reliant-labs[bot] at the pull request’s head commit. Its event is REQUEST_CHANGES when the reviewer found a defect that must be fixed before merge, and COMMENT otherwise. The body has a Defects section, then a Risks section, and ends with a footer naming the model and the commit it reviewed. A clean pull request gets one line: “No defects or risks found in the changed code.”After its first review, the workflow creates two labels in the repository, skip-review and agent:re-review.5
Skip or repeat a review
- Add
skip-reviewbefore opening a pull request, or open it as a draft, and it is not reviewed. - Add
agent:re-reviewto review it again. The workflow removes the label afterwards, so you can add it again later. - Or comment
/autopilot re-review. Only you and the accounts intrusted_idscan trigger it this way.
6
Turn it off
Pass
--project-id. Without it, deactivate pauses this workflow in every project you own.terminal
activate resumes it. reliant trigger delete <id> removes one activation and keeps its firing history.What this does not do
- It never approves or merges. The review event is computed in one node that can only produce
COMMENTorREQUEST_CHANGES, and the reviewer has no tool that posts a review. If you want something to merge, you compose that yourself: a workflow you write can callgithub/pr.merge@1in an action node, pinned to the reviewed head commit (Merging is a workflow step). - It does not run your code. The reviewer reads through GitHub with read-only tools. It runs no tests, builds or linters, so keep your CI.
- It has no budget of its own. Each review is capped at 40 agent turns, and every non-draft pull request is reviewed, including the ones agents open. Start with one repository. See What it costs.
- In an organization with two or more members, runs spend only the organization’s AI accounts by default (
Unattended funding: org_onlyinreliant trigger get). The CLI cannot widen that. A person allows your own accounts on the automation in the app, or an admin adds an organization account.
Troubleshooting
this automation runs only on its organization's AI accounts, and none of them can run the powerful model
this automation runs only on its organization's AI accounts, and none of them can run the powerful model
The run launched but paused at the reviewer, and nothing appears on the pull request.
reliant workflow status <chat> shows Status: PAUSED and call_llm FAIL; reliant workflow follow <chat> prints this error. An admin can add an organization API key or turn on Reliant credits, or you can pick a review_model an organization account can run. The paused run then continues by itself.trigger events shows skipped: filter did not match
trigger events shows skipped: filter did not match
The filter refused the event: the pull request is a draft or carries
skip-review, or the re-review comment came from someone not in trusted_ids. The detail line prints the filter.No firing at all after opening a pull request
No firing at all after opening a pull request
Check that the repository is in
repos (reliant trigger get <id> prints Param repos:) and that the Reliant GitHub App is installed on it.Next steps
Turn issues into pull requests
Label an issue and the issue worker opens a tested pull request for this review.
Add a security review
A second, read-only reviewer that threat-models each pull request.
Autopilot reference
Every setting, label, lease and cost of the five Autopilot workflows.
Who an automation acts as
The Reliant bot, your own account, and the push check behind both.