> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peepsai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Code review settings

> Turn on Peeps code review for a GitHub repository, choose when it reviews and what it comments on, and see what it sends for review.

Peeps reviews pull requests on the repositories you turn on. You set this up one repository at a time, under **Settings** > **Code review** > **Review settings**.

## Who can use it

You need the Owner role.

You also need the [Peeps GitHub App](https://docs.peepsai.com/integrations/github.md) connected, with access to the repositories you want reviewed.

> [!NOTE]
>
> If you don't see **Code review** in settings, it isn't turned on for your organization yet. [Get in touch](mailto:support@peepsai.com) to request access.

## Choose a repository

Pick one from the **Repository** menu. The menu lists every repository the GitHub App can access, with the ones being reviewed first. Beside it, a count such as **2 of 14 running** shows how many are being reviewed.

| In the menu | Means |
| - | - |
| **(on)** | Peeps reviews this repository's pull requests. |
| **(not running)** | It's saved as on, but reviews can't run. See [If reviews stop running](#if-reviews-stop-running). |
| No marker | It's off. |

To add a repository to the menu, [change what the installation can access](https://docs.peepsai.com/integrations/github.md#manage-installations) on GitHub.

## Turn it on

**1. Turn on the switch**

Use the switch beside **Code review is off**. A **Not saved yet** badge appears.

**2. Save**

Click **Save changes**. The heading changes to **Code review is on**.

Turn it off the same way.

## What the settings do

### When to review

| Setting | What it does |
| - | - |
| **Trigger** | **When a PR opens** reviews a pull request when it opens, is reopened or leaves draft. **Every push** also reviews each push. |
| **Skip drafts** | Doesn't review draft pull requests. |
| **Target branches** | Globs over the base branch. Empty reviews every branch. |
| **Ignore paths** | Left out of the review and named as not read. A pull request that changes only these gets a short **Nothing to review** review. |

Peeps doesn't review pull requests from forks or bots, or its own `peeps/*` branches.

### How to review

**Second review** adds an independent second reviewer, then a merge pass that keeps what either found.

### Findings

Set each group to **Comment** or **Ignore**.

| Group | Covers |
| - | - |
| **Critical** | Anything that breaks production |
| **Security** | Injection, leaks, auth gaps |
| **Bugs** | Wrong behavior, races, edge cases |
| **Performance** | Slow queries, needless work |
| **Style** | Readability and consistency |
| **Nits** | Small polish |
| **Team rules** | Your `CLAUDE.md` and review rules |

### Verdict

Each takes a level: **Critical only**, **Major and above** or **Anything**. **Request changes** and **Approve when clean** also have a switch.

| Setting | What it does |
| - | - |
| **Request changes** | Requests changes on the pull request when a posted finding is at or above the level. GitHub stops the merge only if your branch rules require reviews. |
| **Ready to merge** | A complete review with nothing at or above the level, open threads included, is ready: its `Peeps / code review` check goes green and its verdict starts **Looks ready to merge**, unless it requests changes. This works whether or not approvals are on. The default, **Anything**, means a review is ready only when it found no issues and none of Peeps' earlier ones is still open. |
| **Approve when clean** | Approves a complete review with nothing at or above the level, open threads included. A conversation about a lower-level issue doesn't hold back the approval. Approving doesn't change the check: it goes green only when the review is also ready at the **Ready to merge** level. |

### Presets

A preset fills in every setting at once, except **Ready to merge**, which stays as you set it. You still need to save. If you change a setting so that no preset matches, the page shows **Custom settings**.

| Preset | What it does |
| - | - |
| **Ship It** | Reviews when a pull request opens, comments on what matters. |
| **Staff Engineer** | Reviews every push with a second, independent reviewer. |
| **Principal Who Hates You** | Reviews every push, drafts included, with two reviewers, flags everything down to the nits, and requests changes on majors and above. |

**Review quality** scores the current settings out of 99, as **Light**, **Solid**, **Strict** or **Thorough**.

### Static code analysis

The **Static code analysis** section, after **Verdict**, holds the **Complexity check**. Its **Complexity findings** row sets whether the review only lists the functions crossing a limit (**Comment**) or also requests changes for them (**Request changes**). It runs a separate check on each pull request, named `Peeps / static analysis`, which names the functions crossing a limit. It has its own switch, independent of code review's, and presets don't change it. **Save changes** saves it with the rest. See [Complexity check](https://docs.peepsai.com/code-review/complexity-check.md).

If you don't see the section, it isn't turned on for your organization yet. [Get in touch](mailto:support@peepsai.com) to request access.

## Save your changes

**Save changes** saves the switch and every setting for the repository on screen.

Save before you pick another repository. Changing the **Repository** menu drops anything you haven't saved.

## What Peeps sends for review

> [!WARNING]
>
> Turning a repository on sends each pull request's diff and the repository's files at its head to Anthropic and to Amazon Bedrock for review. Files named like secrets, such as .env files and keys, and files renamed from them, are left out.

## If reviews stop running

The heading reads **Code review isn't running** when a repository is saved as on but reviews can't run.

| Cause | What to do |
| - | - |
| The GitHub installation is suspended | Unsuspend it on GitHub. You can't change the settings until you do. |
| The GitHub App was reinstalled since the settings were saved | Click **Save changes**. |

**Can't check right now** means GitHub didn't answer. The switch still shows what you saved. Try again.

***

Questions about code review? [Get in touch](mailto:support@peepsai.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.