## Documentation Index

Fetch the complete documentation index at: [/llms.txt](https://docs.entire.io/llms.txt)

Use this file to discover all available pages before exploring further.

Use this page when you want `entire review` to use a saved review setup. A review profile tells Entire which agents should review a branch, which agent should judge the results, and where the final verdict should go. For command syntax, see the [`review` command reference](https://docs.entire.io/cli-reference/review). For a complete review workflow, see [Review and Recap Agent Work](https://docs.entire.io/learn/review-and-recap-agent-work).

## What this config affects

Review profile settings control:

- named profiles you can run with `entire review PROFILE`
- the default review profile
- reviewer agents, judge agent, output mode, task text, model choices, and reviewer slots
- whether the review setup is shared with the repository or kept local to your machine

## Configure review profiles

- Shared project profile
- Local profile

Use a shared project profile when the team should run the same review setup for this repository. Create or update a profile with:

```
entire review --configure
```

You can also configure a profile without the interactive setup:

```
entire review --configure \
  --set-agents codex,claude-code \
  --set-judge codex \
  --set-output local
```

By default, `entire review --configure` saves the profile to `.entire/settings.json`. Commit `.entire/settings.json` when the review profile should apply to everyone working in the repository.

Use a local profile for personal reviewer choices, private model preferences, or temporary review experiments. Add `--local` when the profile should be saved only on your machine:

```
entire review --configure --local
```

You can combine `--local` with non-interactive setup flags:

```
entire review --configure --local \
  --set-agents codex \
  --set-judge codex \
  --set-output local
```

Local review profiles are saved to `.entire/settings.local.json`. Local settings have higher priority than shared project settings, so use them when your review setup should not affect teammates.

## Review profile settings

`entire review --configure` manages these setting paths:

| Setting path                   | Type   | Use for                                        |
| ------------------------------- | ------ | ----------------------------------------------- |
| `review_default_profile`       | string | The default review profile name                  |
| `review_profiles`              | object | Named review profiles and their reviewer, judge, output, task, model, and slot settings |

Use `entire review --configure` or `entire review --edit` to update review profiles when possible. The profile JSON can contain nested reviewer and model settings, so the CLI is the safest way to keep the shape valid.

## Modify review profiles

Use the review command to change saved profile settings:

```
entire review --configure
entire review --configure --set-agents codex,claude-code --set-judge codex
entire review --edit
```

Use `--local` when the change should be personal:

```
entire review --configure --local
```

## Verify review profiles

After configuring review profiles, list them:

```
entire review --list
```

To see the reviewers for the selected profile, run:

```
entire review --agents
```

Run a named profile with:

```
entire review general
```

If the review uses the wrong agents or output mode, check whether a local profile in `.entire/settings.local.json` is overriding the shared profile in `.entire/settings.json`.