← All use cases

PR review & digest

A reviewer on every pull request, and a digest on Friday.

An agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.

Get started free
Book a demo

How it works

Three steps to a standing task

  1. Step 01

    Teach it your conventions

    Point the agent at your contributing guide and let it read recent reviews. It learns what your team actually comments on rather than generic style advice.

  2. Step 02

    Attach a GitHub trigger

    Run the reviewer on `pull_request.opened` and `pull_request.synchronize`, filtered to the base branches you care about. Add a label filter if you want to opt PRs in one at a time.

  3. Step 03

    Read the review, and the weekly digest

    The agent posts inline comments where they belong. A scheduled sibling posts the Friday digest to your engineering channel.

The run

What the agent actually does

Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.

github · pull_request.opened

Review new pull requests against our conventions and leave inline comments.

  1. github·fetch the diff for PR #2841
  2. github·read CONTRIBUTING.md and recent reviews
  3. code·run analysis over the changed files
  4. github·post a review with 3 inline comments
  5. slack·notify the author in #eng

Review posted on PR #2841

  • Flagged an unhandled error path in `sync.ts:142`
  • Suggested reusing `parseCursor` instead of a second parser
  • Confirmed the migration is backward compatible
  • Author notified with a link to the review

Reach

The tools this agent touches

Each one connects once, and the agent gets its complete API.

This task belongs to Engineering. See the rest of what that team hands off.

FAQ

Questions, answered

Put an agent on pr review & digest.

Describe the task, attach a trigger, and let it run around the clock.

Get started free
Book a demo