> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/verify/how-to-guides/verify-on-github.md).

# Review verification on the pull request

With the [Aviator Chrome extension](/aviator-chrome-extension.md), a **Verify** tab appears in the pull request's tab row, next to Files changed. It's a trimmed-down, live view of the review document, so you can see why verification failed and unblock the PR without leaving GitHub.

<figure><img src="/files/8ViX3XGNklygelW8oGZp" alt="The Verify tab selected on a GitHub pull request, showing a failed run header with rerun and open-in-Aviator buttons, four passing acceptance criteria, a failing invariant with its reason, and a waived invariant struck through with its category and reason"><figcaption><p>The Verify tab on a pull request with a failing run</p></figcaption></figure>

### Prerequisites

* The [Aviator Chrome extension](/aviator-chrome-extension.md) installed and signed in to Aviator.
* The pull request has a verification run. The tab only appears once a run exists; PRs without one show nothing.
* An Aviator backend on version `2026.07.16-2` or newer. Aviator Cloud is always current. A self-hosted deployment older than that doesn't serve the data the tab reads, so the tab stays hidden.

### What it shows

The tab opens in place of GitHub's content and mirrors the review document:

* **The run outcome** — passed, passed with N accepted failures, failed, errored, in progress, or deferred (waiting on invariant selection).
* **The verified commit** and when and why the run happened (for example, "9 days ago on queue").
* **Every criterion and invariant** with its verdict icon and, for failing rows, the reason it failed. Invariants appear in their own section and link to their invariant page.
* **Waived rows** are struck through and show the waiver's category and reason.

The outcome tracks the `aviator/verify` check, so the tab never disagrees with it — a run that failed but has every failure waived reads as passed with accepted failures. Live updates arrive on their own; you don't need to refresh.

Use **Open in Aviator** for the full review document (evidence, scenarios, run history).

### Rerun verification

Select **Rerun verification** to start a new run against the PR's latest commit. It's unavailable while a run is in progress, and when the runbook has no open PR to verify against it explains why.

### Waive an invariant failure

Failing invariant rows offer **Waive…**. Invariants are account-wide rules you can't edit here, so failures clear by waiving them:

1. Pick a category — **False positive**, **Doesn't apply**, **Accepted risk**, or **Fix in follow-up**.
2. Give a reason (required).
3. Confirm. The failure clears, the counter and header update, and the `aviator/verify` check is re-posted.

<figure><img src="/files/PUQVMupaZi4OtMCxplEm" alt="The waive dialog showing the invariant text, a category dropdown set to False positive, and a required reason field" width="496"><figcaption><p>Waiving an invariant failure with a category and a reason</p></figcaption></figure>

### Remove an acceptance criterion

Failing acceptance-criteria rows offer **Remove…**, which drops a criterion you don't want verified. The last remaining criterion and account invariants can't be removed; when the backend refuses, the tab tells you why.

### Related

* [Fixing verification failures](/verify/how-to-guides/fixing-verification-failures.md) — the failure shapes and how to resolve each.
* [GitHub integration](/verify/reference/github-integration.md) — the `aviator/verify` check and its states.


---

# 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://docs.aviator.co/verify/how-to-guides/verify-on-github.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.