AI Review tab

The AI Review tab is where you run an AI review of the pull request, read what it found, and choose what to post to GitHub. The review runs on your own Claude or Codex sign-in. The number on the tab counts the findings that are open now. This page describes the tab; the AI review section explains the review itself.

#Run a review

Under Run a review, choose a model (or leave the default) and press the run button. The button has two modes, on its arrow:

• Review only: the review stays in Limn until you post it. This is the default.
• Review and post: the review is posted to GitHub when it is done, under your account, following the workspace's posting rules.

Once a review exists, the button reads Re-review only or Re-review and post. Limn remembers your last choice. While a review runs, the tab shows its progress and a stop button. See Run a review.

#What you see

The tab reads top to bottom (on a wide screen, the facts and actions sit in a column on the right):

• Where this PR stands: the pull request's latest commit (seven characters; click it to open it on GitHub, or copy the full commit), then one row per person, in the same columns as the reviews below: the verdict GitHub holds for them, with its date, time and commit.
• Reviews on this PR: every review, newest first, in columns: who, the date and time (24-hour clock), the commit it reviewed, the outcome, and what ran it. On your own pull request GitHub takes only a Comment from you, so a review of yours that approved reads Approve (posted as Comment). Match a review's commit against the latest commit above. The newest 10 show; Show all opens the rest. Click a review to open it read-only. A run's cost is behind the ⓘ beside its summary.
• Summary: what the change does and the review's main points. The models and the cost are behind the ⓘ.
• Review threads: the AI's judgement of the open threads from people and bots. Not shown when there are none.
• Findings: each finding with its severity, the code it is about, and who raised it. Open lists every finding still open, earlier ones included; Resolved or addressed lists the rest. An earlier finding says in one line how it was dealt with, or what is still needed. See Follow-up reviews.
• Story check, the CI check, SonarCloud and Reference docs, where those are set up. See Story checks.
• Design: diagrams of the change. See Design diagrams.
• Review chat: ask about the review. See Review chat.

#Post to GitHub

Tick the findings to keep, reword any of them, write or edit the summary, and choose the verdict. Use the preview, then post. Everything you post goes to GitHub as one review under your account. See Verdicts and posting.

Fix what it found

Generate fix from this review hands the review's findings to the AI Fix tab, where you choose what to fix.