Code review

Code review is an agent you define

Deploy a review agent in YAML: it reacts on every head advance of a pull request, reviews only the commits it has not seen, and runs the suite before it comments. Any coding agent can write slop; yours is the one that catches it before merge.

Install on GitHubDocumentation
Comments posted by severity
Last 30 days · splitshift-hq · 1,068 comments
Median review 2m
4003002001000
58
196
372
318
124
Blocking
High
Medium
Low
Trivial
agents/code-reviewer.yamllive on merge
ellipsis:  version: v1  name: Code Reviewer  description: Review the new commits on every pull requestclaude:  model: claude-haiku-4-5-20251001  system: |    Review only the new, unreviewed commits. Flag correctness    bugs, security issues, and breaking changes. Suggest the fix    on the exact line. Skip pure style; a linter handles that.trigger:  type: react  code_review:    repositories: [splitshift-web, splitshift-api]    for:      users: true      bots: falsebudget:  session: 0.30  day: 3.00

Your reviewer, not ours

Write the review standard into the agent

The prompt, the model, the repositories it watches, and the spend caps are all yours, in one file in your repository. Tune what it flags and what it ignores the way you tune a linter, and ship the change as a pull request.
splitshift-api #512never re-comments a reviewed line
push 13 commits
reviewed a4f1…9c022 comments
push 21 commit
reviewed 9c02…e7b81 comment
push 32 commits
reviewed e7b8…1d40no findings

Incremental by default

Every push is reviewed once

The agent reviews only the commits it has not seen yet, anchored at the head it reviewed last. Authors get feedback on what they just pushed instead of the same comments on the same lines, so a long-running branch never turns into review noise.

# reviewing splitshift-api#512, push 2

$ pytest -k trade

14 passed

$ git diff HEAD~2 -- src/trade_engine.py

reads the actual change, runs the actual suite, then comments

It runs the code

A reviewer with a sandbox, not just a diff

The agent gets your repository on disk with the toolchain installed, so it can run the suite, reproduce the failure, and check the behavior it is worried about. A finding it verified is a finding worth reading.
splitshift-api #512 · comments

marcus-lee

@ellipsis use the staging database, not prod

👀 · conversation woken, same working tree

ellipsis[bot]

Switched the fixtures to the staging database and re-ran the suite: 12 passed. Pushed the change to this branch.

one message to steer, no kill-and-restart

One conversation per pull request

Reply on the PR and it answers

The review is a durable conversation that remembers the whole pull request. Push back on a finding, ask it to fix what it found, or tell it to use the staging database, and it picks up with its working tree intact. Merge closes the conversation.

More ways teams use agents

Development

Cloud coding agents unlock parallelization

Automations

Automate everything with cloud agents

Every use case runs on the same platform. See how it works