Ask about a review

A finding is short by design. When you want to know more (why it matters, whether it really applies, what a fix would look like), ask in the Review chat. The chat knows the whole review and the code it read, so you do not have to explain the context.

#Ask a question

1. Open the pull request's AI Review tab. The Review chat section is under Story check and open by default. Hide closes it; when it is closed, the button to open it reads, for example, Ask Claude about this review.
2. Type your question.
3. Press Ask. The question shows at once and the answer follows. The button reads Answering… meanwhile.

There is one chat per review, and it covers every finding. A new review of the same pull request starts with an empty chat. One answer runs at a time.

#Explain findings

1. On a finding, press Send to chat. It is pinned to the chat as a pill. You can pin up to ten, including a story check's unmet items.
2. Add a question if you want, or just press Ask to explain them.
3. Read one card per pinned item: What it means, Why it matters, where it is, and What would fix it.

#What it can read

• The pull request's title and description, the review's verdict, summary and every finding, with your rewording.
• The ticket's story and its check, and the follow-up of earlier findings.
• After a deep review: the repository at the commit that was reviewed, so it can open other files. After a quick review: the diff only.

The chat can read; it cannot change files, run commands or reach the web. If the pull request has new commits since the review, the chat says Answers are about the reviewed commit; the PR has moved on. Run a new review to talk about the new code.

#Earlier chats

Earlier reviews' chats, under the chat, lists the chats of earlier reviews of the pull request. Pick one to read it. Earlier chats are read-only.