> 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/how-deep-review-works.md).

# How Deep Review Works

Deep Review is Aikido's agentic pull request reviewer. Instead of treating the diff as the full story, Aikido explores relevant code, reasons about the wider impact of a change, and posts feedback directly on your pull request.

## Context beyond the diff

A diff shows what changed, but not always how that change interacts with the rest of your application. Deep Review pulls in relevant context from outside the changed lines before deciding whether to comment, so it can review changes that depend on existing behavior elsewhere in the codebase.

## Cross-repository context

If your application spans multiple repositories, you can [link related repositories](/deep-review/link-repositories.md) to the repository under review. Deep Review can then use those repositories as additional context when reasoning about shared libraries, APIs, and services.

The number of repositories you can link depends on your Aikido plan.

## Feedback in your pull request

Aikido posts comments directly on your pull request when Deep Review has feedback to share. You don't need to leave your existing review workflow to see or discuss the results.

When you fix an issue that a comment identifies, Aikido automatically resolves the comment. [Learn how Aikido manages comments after an issue is fixed](/pr-and-release-gating/aikido-ci-gating-functionality/autofix-suggestions-and-inline-commenting-for-pr-checks.md#what-happens-to-comments-after-you-fix-an-issue).

### Reply in natural language

Reply to any Deep Review comment in plain language. You don't need to tag Aikido or use a special command format, and you can stay in the pull request without switching to the Aikido UI.

| What you say                   | Example                                                  | Status                                                                                                          |
| ------------------------------ | -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Ignore a finding**           | "This is a false positive, please ignore."               | Available now. Aikido ignores the finding.                                                                      |
| **Share context or push back** | "This is intentional because we validate on the server." | Available now. Aikido uses the feedback to improve future reviews. Shared memory across reviews is coming soon. |
| **Ask for clarification**      | "Can you explain why this is a problem?"                 | Coming soon                                                                                                     |
| **Request a follow-up**        | "Suggest a safer alternative."                           | Coming soon                                                                                                     |

## Credits

Deep Review costs **1 credit per pull request per rolling 24-hour window**. Additional reviews on the same PR within that window (for example after new commits) don't cost extra. When you're out of credits, Deep Reviews are skipped.

{% 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 %}

Learn how to [configure Deep Review](/deep-review/configure-deep-review.md).


---

# 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/how-deep-review-works.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.