Check how far the review got
Find the Claude Code Review check run on your pull request, then match its title to one of these common ones:A review didnât start
Check these cases when no Claude Code Review check run appears, or when Claude posts a comment saying the review was skipped.A comment command didnât start a review
After you comment@claude review, look for a Claude Code Review check run titled Code review queued⌠or Code review in progress⌠on the pull request. An đ reaction on your comment doesnât confirm a review is coming. If no check run appears, check for each of these causes:
- Code Review isnât on for this repository: Claude posts no comment and no check run in response to the command. Ask an Owner to add the repository.
- The comment doesnât meet a condition: it was an inline comment or a review body rather than a new top-level comment, or the command wasnât at the start of the comment. Editing an earlier comment instead of posting a new one doesnât count either, and the pull request has to be open. See the conditions for comment commands and post a new comment that meets them.
- You donât have write access: you need write, maintain, or admin permission on the repository. On a pull request from a fork, the permission that counts is on the base repository. Unless the pull request is yours, Claude can reply with a tip: âNo review was started: manual reviews can only be requested by someone with write access to this repository.â Ask someone with write access to comment instead.
- The budget ran out: Claude posts a comment that begins with ââ ď¸ Code review skippedâ. See Review didnât run and the PR shows a budget message.
Review didnât run and the PR shows a budget message
When your organizationâs budget canât cover a review, Code Review skips the review and Claude posts a comment on the pull request that begins with ââ ď¸ Code review skippedâ. In some of these cases a check run titled Code review declined also appears. The comment links claude.ai/admin-settings/usage, where an admin restores the budget. Its wording tells you which limit was reached:- âhas reached its monthly code review spending capâ: the monthly spend limit for Code Review was reached. Reviews resume at the start of the next billing period. To get them sooner, ask an admin to raise the limit.
- âhas no extra usage available to pay for this reviewâ: your organizationâs usage credits balance is empty, or its overall monthly spend limit was reached. Ask an admin to add usage credits or raise that limit.
- âis too low to start another reviewâ: whatâs left of the budget or balance is less than the expected cost of one review. Ask an admin to raise the limit or add usage credits.
@claude review on the pull request to get the review that was skipped. The conditions for comment commands apply, so the commenter needs write access.
Retrigger a failed or timed-out review
If the check runâs summary says âThe review session was interrupted before it could finish. A new review of this commit has been queued automatically.â, you donât need to do anything. That review is retried once automatically. Otherwise, when the check runâs title is Code review failed or Code review timed out, run the review again with a comment or a re-run:- Comment
@claude review: post it as a top-level comment on the pull request. This starts a fresh review without subscribing the pull request to future pushes. - Click Re-run: if the pull request isnât from a fork, click Re-run on the Claude Code Review check in GitHubâs Checks tab. The re-run covers the pull requestâs current head commit and doesnât subscribe the pull request either.
Find issues that arenât showing as inline comments
If the check run title says issues were found but you donât see inline review comments on the diff, look in these other locations where findings are surfaced:- Check run Details: click Details next to the Claude Code Review check in the Checks tab. The severity table lists findings with their file, line, and summary regardless of whether the inline comment was accepted.
- Files changed annotations: open the Files changed tab on the PR. A finding that has a line but wasnât posted as an inline comment appears there as an annotation on the lines concerned.
- Whole-file comments: open the Conversation tab on the PR and look for a comment from Claude on a whole file instead of on a line
- Review body: in the Conversation tab, look for an Additional findings heading in Claudeâs review
The check run mentions REVIEW.md
These are four of the messages a check run can carry aboutREVIEW.md:
- âThis review applied the repositoryâs review instructions (REVIEW.md) from its default branch, which is not protected against direct pushes.â: the review read the root file only. See Which branch REVIEW.md is read from for what protecting the branch changes.
- âwere not applied to this review: branch protection could not be confirmedâ: the review read no
REVIEW.md. - âthey link to a file this pull request modifies, or carry more links than the review checksâ: the review skipped the root
REVIEW.md, or the number of subdirectoryREVIEW.mdfiles the message gives. Check the skipped file for each cause. For the rootREVIEW.md, check the files it includes too:- Too many links: it carries more than 64 Markdown links. Cut links to 64 or fewer.
- A link the review canât parse: it has a malformed Markdown link. Fix or remove the link.
- A link to a changed file: it links to a file or folder this pull request changes, and the review couldnât leave out only the lines with that link. Write the rule in
REVIEW.mditself.
- âinclude line(s) in the root REVIEW.md were skipped on this reviewâ: your root
REVIEW.mdapplied, but the files those lines name didnât. Check the lists under Include other files in REVIEW.md and, for a skill, under Include a skill file.
Setup problems
These cases come up for an Owner while setting up Code Review.A repository isnât listed in Add a repository
Search for the repository by name first, because the dialog doesnât load a long list in full. The dialog lists a repository only if the Claude GitHub App can access it. Click Install GitHub App and give the app access to the repository. When no repositories are listed, Install GitHub App is a button in the dialog. Otherwise, itâs at the bottom of the dialogâs GitHub organization filter menu.No check run appears on the test pull request
Confirm that Allow code review is on, that the repository is listed under Repositories in the Code review section, and that the Claude GitHub App has access to it. Automatic reviews skip draft pull requests, and a repository set to Manual (@claude review) needs an@claude review comment to start the first review.
Related resources
- Read and request reviews on a pull request: what the findings and the check run mean, and the comment commands
- Set up Code Review: for Owners, turn on Code Review and manage repositories
- Code Review costs and usage: the spend limits behind a budget message
- Customize Code Review: which copy of
REVIEW.mda review reads