Review the PR like the author walked you through it.

1. 00

   point it at a PR

   One command, your machine, your subscription.

   Run ARGUS: Review PR… from the command palette and paste a PR URL or owner/repo#number. It fetches through your own gh CLI and drives your already-authenticated Claude CLI for the review — no server, no upload, no per-seat SaaS. Or run Open Demo Review to try it with zero setup.

   ⌘⇧P ARGUS: Review PR…
     https://github.com/acme/api/pull/482
     fetched via your gh CLI · nothing uploaded
     enter to review ↵

2. 01

   state the intent

   Reviews against intent, not guesses.

   Argus works out what the change is actually for and states it explicitly on the Overview tab — then grounds every note in that intent, so a deliberate choice reads as intentional instead of being mistaken for a slip. Each note is anchored to the first changed line of its hunk, never landing on the wrong one.

   intent · overview tab

   “harden secret redaction before any prompt leaves the
    process — mask hyphen-delimited keys like x-api-key, and
    stop a `==` comparison losing its operator.”
   shown explicitly on the Overview tab
   so    every note is grounded in this intent, not a guess

3. 02

   files first, review streams in

   Start reading before the AI does.

   The Changed Files tree and the Overview open instantly — click any file to start reading its diff, no waiting on the model. The skeptic notes stream in behind a status indicator and attach to each hunk as they land, so nothing blocks.

   on open

   files tree   ready
   overview     ready
   diff         click a file
   notes        ⠋ streaming…

   moments later

   redact.go    ▌ why · look out
   claude.go    ▌ why · look out
   parse.go     ▌ why · look out
   …
   overview     ready

4. 03

   the reviewer-skeptic lens

   Every hunk: why it changed, and what to watch.

   For each hunk Argus asks the two questions a careful reviewer would — why this change, in plain language, and look out for: what could go wrong, what to double-check, what the author may have missed. They render as native comment threads on the diff, tagged by importance — and Argus reports any hunk it couldn't cover, so a gap never passes for a clean bill.

   thread redact.go · hunk 1 · importance: critical

   ▌ why this change
     refuses a leading “=”, so “if x == y” no longer
     masks its second “=” mid-comparison.
   ▌ look out for
     widened key class could over-mask a value that
     merely contains “key”. ← confirm

5. 04

   the overview tab

   The whole PR, before the first hunk.

   One tab frames the change: a plain-language summary, the explicit intent, the critical things to verify before approving, and an understand-the-flow walkthrough end to end. A streaming chat panel you can dock beside your diff handles anything you don't follow, scoped to the file you have open.

   overview acme/api#482

   summary   harden secret redaction before prompts leave the process
   intent    mask hyphen-keys · stop “==” losing its operator
   critical  · confirm the widened key class won't over-mask
             · redaction runs before any prompt is sent
   flow      1 orchestrator → 2 redact → 3 claude adapter

6. 05

   your call, straight to GitHub

   Comments inline, your review to the PR.

   Skeptic notes render as comment threads on the diff (marked ▌ so they're never mistaken for a +/− line), the Changed Files tree tracks a reviewed toggle per file that persists across reloads, and you can add your own comments on diff lines — then submit them as one GitHub review: comment, approve, or request changes, without leaving VS Code.

   argus redact.go · ▓▓▓▓▓▓░░░░ 12/23 reviewed · native diff · comment threads · submit to GitHub

   changed files

   orchestrator.go
   claude.go
   ▸ redact.go
     redact_test.go
     parse.go
     …

   diff · ai comment thread

   ▌ why · the value pattern refuses a leading
   ▌ “=”, so a “==” comparison's second “=”
   ▌ isn't swallowed. look out for: the widened
   ▌ key class could over-mask a value with “key”.
   @@ internal/agent/redact.go · assignmentRule
     …secret|api[-_]?key|access[-_]?key…
   - )("[^"]+"|'[^']+'|[^"'\s,}]+)
   + )("[^"]+"|'[^']+'|[^"'\s,}=][^"'\s,}]*)

   your review

   add a comment on this line…
   
   submit as one review
   comment
   approve
   request changes

   chatask Argus about the open file▮

   needs you

   The look out for note puts the one thing worth confirming right in front of you: check that the widened key class won't mask a legitimate value that just happens to contain “key”. Everything else in the file is safe to skim.

Once you know why a change was made, most of the diff is safe to skim.