Code Review changedcode-review
Nearest release: v2.1.283, published 6 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 26 Sep 2026 01:09 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 28 Sep 2026 23:37 UTC.
Upstream edited
Recorded here
Lines+18added
Lines−18removed
From line
34
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits16to this page, all time
The whole hunk
from line 34, old and new numbered
/
from line 34
3434
3535Each finding is tagged with a severity level:
3636
37| Marker | Severity | Meaning |
38| :----- | :----------- | :------------------------------------------------------------------ |
39| 🔴 | Important | A bug that should be fixed before merging |
40| 🟡 | Nit | A minor issue, worth fixing but not blocking |
41| 🟣 | Pre-existing | A bug that exists in the codebase but was not introduced by this PR |
37| Marker | Severity | Meaning |
38| :- | :- | :- |
39| 🔴 | Important | A bug that should be fixed before merging |
40| 🟡 | Nit | A minor issue, worth fixing but not blocking |
41| 🟣 | Pre-existing | A bug that exists in the codebase but was not introduced by this PR |
4242
4343Findings include a collapsible extended reasoning section you can expand to understand why Claude flagged the issue and how it verified the problem.
4444
from line 54
5454
5555Beyond the inline review comments, each review populates the **Claude Code Review** check run that appears alongside your CI checks. Expand its **Details** link to see a summary of every finding in one place, sorted by severity:
5656
57| Severity | File:Line | Issue |
58| ------------ | ------------------------- | -------------------------------------------------------------- |
57| Severity | File:Line | Issue |
58| - | - | - |
5959| 🔴 Important | `src/auth/session.ts:142` | Token refresh races with logout, leaving stale sessions active |
60| 🟡 Nit | `src/auth/session.ts:88` | `parseExpiry` silently returns 0 on malformed input |
60| 🟡 Nit | `src/auth/session.ts:88` | `parseExpiry` silently returns 0 on malformed input |
6161
6262Each finding also appears as an annotation in the **Files changed** tab, marked directly on the relevant diff lines. Important findings render with a red marker, nits with a yellow warning, and pre-existing bugs with a gray notice. Annotations and the severity table are written to the check run independently of inline review comments, so they remain available even if GitHub rejects an inline comment on a line that moved.
6363
from line 118
118118
119119Comment commands start a review on demand. They work regardless of the repository's configured trigger, so you can use them to opt specific PRs into review in Manual mode or to get an immediate re-review in other modes.
120120
121| Command | What it does |
122| :---------------------- | :---------------------------------------------------------------------------- |
123| `@claude review` | Starts a single review without subscribing the PR to future pushes |
121| Command | What it does |
122| :- | :- |
123| `@claude review` | Starts a single review without subscribing the PR to future pushes |
124124| `@claude review always` | Starts a review and subscribes the PR to push-triggered reviews going forward |
125| `@claude review once` | Same as `@claude review`: starts a single review without subscribing |
125| `@claude review once` | Same as `@claude review`: starts a single review without subscribing |
126126
127127Use `@claude review always` when you want every subsequent push to the PR to start a fresh review, such as on a high-priority PR in a repository set to Manual mode. Because the bare command doesn't subscribe the PR, you can request a one-off second opinion without changing whether later pushes trigger reviews.
128128
from line 234
234234
235235Go to [claude.ai/analytics/code-review](https://claude.ai/analytics/code-review) to see Code Review activity across your organization. The dashboard shows:
236236
237| Section | What it shows |
238| :------------------- | :--------------------------------------------------------------------------------------- |
239| PRs reviewed | Daily count of pull requests reviewed over the selected time range |
240| Cost weekly | Weekly spend on Code Review |
241| Feedback | Count of review comments that were auto-resolved because a developer addressed the issue |
242| Repository breakdown | Per-repo counts of PRs reviewed and comments resolved |
237| Section | What it shows |
238| :- | :- |
239| PRs reviewed | Daily count of pull requests reviewed over the selected time range |
240| Cost weekly | Weekly spend on Code Review |
241| Feedback | Count of review comments that were auto-resolved because a developer addressed the issue |
242| Repository breakdown | Per-repo counts of PRs reviewed and comments resolved |
243243
244244Dashboard cost figures are estimates for monitoring activity. For invoice-accurate spend, refer to your Anthropic bill.
245245
No line in this hunk matches that.