Review a coding agent PR with GitHub and CodeRabbit

Use this recipe when: your coding agent should open a PR and you want its GitHub checks and CodeRabbit review recorded against one final commit in a Millwork receipt. You are done when: the packet names the PR, exact final SHA and the outcome of both sources. For the next task, keep the connected repository and agent, refresh the base SHA, and use a new request key.

Set up the first job

Connect GitHub and your coding agent, set CodeRabbit’s approval workflow, then submit and inspect one run.

The review question

Did CodeRabbit approve the agent’s final PR commit with its threads resolved, and did the named GitHub Actions job pass on that same commit?

This recipe uses sources: [coderabbit, github] and combine: all. Its CodeRabbit fact is a GitHub Bot review, not a reading of CodeRabbit prose or CLI JSONL. A missing approval, skipped review or unavailable source yields no_verdict. A failed required GitHub job blocks. The packet shows each source even when the aggregate is decided.

First job
Next job
Adapt the rule

Connect the repository and register an async agent. Connect as a person with repository write access; Millwork opens the PR in that person’s name. The maintained adapter runs your chosen coding agent and pushes only the Millwork run branch.
Add reviews.request_changes_workflow: true to .coderabbit.yaml as shown in the setup step.
Choose one required workflow ID and job name, read the current full base SHA, and submit the sample request.
Inspect decision_packet.artifact.final_sha, both sources and verdict in the execution and receipt.

Keep the verified repository connection, registered agent, source list and combine rule. Refresh base_sha, write a new task objective, review its budget and charges, and send a new request key in Idempotency-Key. Millwork creates a new branch, opens a new PR, and binds review evidence to its new final SHA. The earlier decision packet remains the record for the earlier commit.

For two GitHub jobs, add another { "workflow_id": ..., "job_name": ... } selector. If CodeRabbit is advisory for a team, change combine deliberately and inspect both source results; use veto_sources when a source’s block must always stop the job. A source outage must never be interpreted as an approval. Each run freezes its selected checks, source rules and combine policy at acceptance.

Without CodeRabbit

Use the same run and receipt for a GitHub-only review. Install the Millwork GitHub App, connect your account, and register the coding agent as in the setup guide. You do not need a CodeRabbit setting or seat. Replace the sample request’s review_composer policy with one GitHub source:

{
  "version": "v1",
  "repository": "team/repo",
  "base_ref": "refs/heads/main",
  "base_sha": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "agent_arm_id": "<ready-agent-arm-id>",
  "sources": [
    { "id": "github", "checks": [{ "workflow_id": 123456, "job_name": "test" }], "minimum_approvals": 0 }
  ],
  "combine": "all",
  "veto_sources": []
}

Choose your required workflow and job. This example requires the named check and no human approval. If you set minimum_approvals: 1 or more, arrange for a reviewer other than the connected person: Millwork opens the PR in that connected person’s name, and their own approval cannot satisfy GitHub’s review rule. The decision packet lists the GitHub source and exact final SHA; the run and receipt flow are the same. A missing required approval or incomplete check is not a pass.

This recipe uses the team’s existing GitHub Actions and, when selected, CodeRabbit installation. For private repositories using CodeRabbit, the connected person needs a CodeRabbit seat. A run branch and PR may consume CI and, when selected, CodeRabbit quota. The Review Composer fee defaults to $0.10 per accepted run; your budget must cover it. Check billing.review_composer_fee_usd_per_execution in GET /v1/account for your configured fee. Millwork charges it on top of the coding-agent provider bill and any GitHub or CodeRabbit plan charges. Its receipt records the run and Millwork charge; a zero agent usage report is not a zero provider bill.

Need a check for an already completed CodeRabbit CLI review instead? Recipe E follows that separate customer-run path.

Output checks

Review jobs

Operations recipes

Review a coding agent PR with GitHub and CodeRabbit

Set up the first job

The review question

Without CodeRabbit

Set up the first job

​The review question

​Without CodeRabbit

The review question

Without CodeRabbit