> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/deep-review/configure-deep-review.md).

# Configure Deep Review

Enable Deep Review for one or more repositories from PR Checks. After enabling it, use each repository's settings to choose the strictness level and [link related repositories](/deep-review/link-repositories.md).

{% hint style="info" %}
Deep Review costs **1 credit per pull request per rolling 24-hour window**. Additional reviews on the same PR within that window don't cost extra.
{% endhint %}

## Enable Deep Review

{% stepper %}
{% step %}

### Open PR Checks

Go to **Repositories > Pull/Merge Requests > Manage PR/MR Checks**. You can also open [Manage PR/MR Checks](https://app.aikido.dev/repositories/prs) directly.
{% endstep %}

{% step %}

### Select repositories

Select one or more repositories. To enable them in bulk, select every repository you want to configure, then click **"Setup PR Scans"** in the bulk actions bar.
{% endstep %}

{% step %}

### Turn on Deep Review

Open the **Deep Review** section and turn on **Perform Deep Review of PRs**.
{% endstep %}

{% step %}

### Save your changes

Click **"Save"**. Aikido will review future pull requests for the selected repositories.
{% endstep %}
{% endstepper %}

<div data-with-frame="true"><figure><img src="/files/krjYwQtasWg6As5efZtz" alt="Repository configuration with Deep Review enabled and the Perform Deep Review of PRs toggle turned on."><figcaption></figcaption></figure></div>

## Open the Deep Review settings for a repository

Strictness and linked repositories are configured separately for each repository:

1. Open [**Repositories**](https://app.aikido.dev/repositories) and select the repository you want to configure.
2. Open its **Repository Settings**.
3. Find the **Deep PR Review** card.
4. Click **"Edit"** next to **Strictness** or **Linked Repositories**.

<div data-with-frame="true"><figure><img src="/files/WC2tVe93RZHY2InoCYNf" alt="Deep PR Review card in repository settings, with Edit buttons for strictness and linked repositories."><figcaption></figcaption></figure></div>

## Choose a strictness level

Strictness controls how much feedback Deep Review posts:

* **Chill**: Keeps reviews focused with fewer comments.
* **Normal**: Provides balanced coverage without overwhelming reviewers.
* **Assertive**: Flags more potential issues and improvements, resulting in more comments.

## Credits

Deep Review costs **1 credit per pull request per rolling 24-hour window**.

That means:

* The first Deep Review on a pull request costs **1 credit**.
* Further reviews on the **same PR** within the next 24 hours (for example after new commits) **don't consume extra credits**.
* After the 24-hour window rolls forward from the last charged review, the next review on that PR costs **1 credit** again.

Credits are charged per PR, not per commit or per individual review run. Learn more about [Aikido Credits](/miscellaneous-info/wallet-and-credits.md).

{% hint style="info" %}
Curious what Deep Review would cost for your team?

Our [estimator](https://app.aikido.dev/repositories/deep-review) gives you an idea based on your activity of the last 30 days.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.aikido.dev/deep-review/configure-deep-review.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.