Review cardPro
An agent's code review in one card: the verdict, open findings by severity, and each finding with its file and line, a suggested fix as a diff, and Apply fix / Dismiss / Reopen.
oxyn add review-cardThe ? on verify turns a store outage into a generic error, so locked-out users see “wrong password”.
−Removed: let ok = verify(pw, &user.salt)?;+Added: let ok = verify(pw, &user.salt).map_err(AuthError::Store)?;
The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.
Rendered from Rust at build time · goes live when visible
When to use
- The user asks the agent to review a diff, a branch or a PR (or a reviewer agent runs automatically after edits).
- They want to know is it safe to ship, what are the real problems and where, and can I fix them in one click — then clear the list.
- Research note 03 lists the "code-review findings card" as common: Claude desktop /code-review → card grouped by file with Walk through in diff, Fix this one, Apply fixes (★ the walk-through stepper); Codex /review with prioritized findings; Verdent Review Changes → Code Review tab; Jules critic; Cursor Bugbot / Agent Review.
- The Codex app shows an automatic review item with review status and risk level (approved / denied / stopped / timed out) — ★ "a visible reviewer verdict chip" (note 03).
When not to use
- Review an agent's change set: use Diff viewer instead.
- A 3-way merge editor: use Merge conflict instead.
- A run as a line of checkpoints, like git for agents: use Checkpoint lanes instead.
Installation
Review card is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.
oxyn add review-cardUsage
The preview is free. Pro opens the code of every Pro component, screen and template.
Examples
Findings
Verdict, counts and findings with fixes.
The ? on verify turns a store outage into a generic error, so locked-out users see “wrong password”.
−Removed: let ok = verify(pw, &user.salt)?;+Added: let ok = verify(pw, &user.salt).map_err(AuthError::Store)?;
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
No nits
Nits hidden.
The ? on verify turns a store outage into a generic error, so locked-out users see “wrong password”.
−Removed: let ok = verify(pw, &user.salt)?;+Added: let ok = verify(pw, &user.salt).map_err(AuthError::Store)?;
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
ReviewCard
| Prop | Type | Default | Description |
|---|---|---|---|
findingsrequired | Vec<Finding> | — | Findings. |
reviewer | String | "Review agent" | Reviewer name. |
subject | String | Default::default() | What was reviewed ("PR #48 · 6 files"). |
expand_first | bool | true | Start with the first finding open. |
hide_nits | bool | Default::default() | Hide nits. |
on_change | EventHandler<(String, FindingState)> | — | A finding changed state. |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| EnterorSpace | Open a finding; press Apply fix, Dismiss or Reopen |
Accessibility
- The verdict is a status; severities are words, not colour alone.
- Finding headers toggle their body and report aria-expanded; fixes read “Removed:” / “Added:”.
From the spec
- Card name: "Agent review of feature/auth-refresh, changes suggested, 1 critical, 2 warnings, 3 nits, 6 unresolved".
- Structure.
articlewith heading; each severity / file group is a labelledlist; each finding is alistitemwith heading "Critical: Race between refresh and logout, src/auth.rs line 142". - Fix preview is a labelled region "Suggested fix, 3 lines added, 1 removed" with the diff readable line by line ("removed: …", "added: …").
- Announcements (polite): "Review finished: changes suggested, 6 findings" once; "Fix applied" / "Finding dismissed as false positive" / "Resolved, 5 left". Streaming findings are not announced individually (only a count every 10 s while reviewing, proposed). Assertive: fix failed, post failed.
- Keyboard: ↑/↓ between findings; Enter go to line; A apply fix; D dismiss (opens reason menu); Shift+R resolve; O reopen; W walk through; Esc stop review / close menus. Keys act only within the focused card.
- Contrast. Severity text labels ≥ 4.5:1; glyphs ≥ 3:1; struck dismissed titles stay ≥ 4.5:1.
- Focus. After Apply / Dismiss, focus moves to the next open finding (announced); never lost to the document when a row collapses.
- Reduced motion. §6 last row.
Motion & interaction
- Streaming findings. Each finding enters with
dur.row.enterand slots into its severity group; groups keep a stable order (Critical → Info) and a finding never moves after it has rendered — new ones append to their group (no reshuffle under the pointer). Group counts and verdict counts roll (dur.count.roll). - Verdict reveal. On
Done, ◇ → ◆ fills (160 ms) and the verdict chip crossfades from "Reviewing…" to its verdict, tinting over 300 ms; no celebration on "Looks good" beyond a ✓ stroke draw. - Link to line. Hover
file:lineshows the 3 surrounding lines in a hover card after 400 ms; click scrolls the diff viewer to the line and pulses its gutter once in the severity colour (600 ms). - Walk through. A stepper "1 of 6" pins to the card header; Next moves focus to the next open finding and scrolls the diff viewer to it (Claude's walk-through-in-diff idea, note 03); the card scrolls so the finding sits at the top of its viewport.
- Apply fix. Fix preview's
+lines briefly brighten, Apply label → "Applying…" (one cell), then ✓ and a file-edit chip slides out from the button (160 ms). The finding dims and, after a 1.2 s hold, collapses to one line (dur.collapse), unless it is focused. - Dismiss. Menu of reasons; choosing one strikes the title left → right (200 ms) and dims; the row collapses after 1.2 s; a 5 s "Undo" toast appears.
- Resolve. Check draws in the row's glyph (
dur.check.draw), row dims; resolved count rolls. - Cleared. When the last open finding closes, the verdict chip morphs to ✓ "All findings addressed" and the card folds after 4 s (like the status strip's Done hold).
- Stale. Amber strip slides in from the header (200 ms); outdated line links get a dashed underline.
- Hover / press. Row tint 80 ms; buttons press scale 0.97 for 80 ms.
Timing
| Transition | Duration | Delay | Easing / spring | Stagger | Frame rate |
|---|---|---|---|---|---|
| Finding enter | 200 ms height + 160 ms fade | 0 | spring.snap / ease.out | 40 ms cap 6 | 60 Hz |
| Count roll (groups, verdict) | 280 ms | 0 | ease.out | 30 ms right → left | 30 Hz |
| "Reviewing…" shimmer | 1400 ms sweep / 800 ms rest | 600 ms | ease.coast | — | 30 Hz |
| ◇ → ◆ + verdict crossfade | 160 ms + 300 ms tint | 0 | spring.snap / linear OKLab | — | 60 Hz |
| Hover card | 160 ms | 400 ms | ease.out | — | 60 Hz |
| Gutter pulse at line | 600 ms ×1 | after scroll | ease.in-out | — | 60 Hz |
| Walk-through scroll | 260 ms | 0 | ease.in-out | — | 60 Hz |
| Apply label swap / chip out | 120 ms / 160 ms | 0 | ease.out / spring.snap | — | 60 Hz |
| Resolved / applied collapse | 280 ms | 1200 ms hold | ease.in | — | 60 Hz |
| Dismiss strike | 200 ms | 0 | ease.out | — | 60 Hz |
| Undo toast | 5000 ms hold, 160 ms in / out | 0 | ease.out / ease.in | — | 60 Hz |
| Batch bar step | 300 ms per change | 0 | ease.out | 120 ms cap 6 | 30 Hz |
| Cleared fold | 280 ms | 4000 ms hold | ease.in-out | 20 ms per row cap 6 | 60 Hz |
| Stale strip in | 200 ms | 0 | ease.out | — | 60 Hz |
| Reduced motion | findings appear with 80 ms fade and instant height; counts swap; no shimmer (static ◇ + "Reviewing 5 of 12 files"); no strike draw (strike appears), no pulses (line gets a static 2 px bar for 4 s), no auto-collapse animation (instant), walk-through jumps | — | linear | none | event-driven |
Responsive behaviour
- Finding headers wrap the file and line under the title on narrow cards.
Edge cases (spec)
- No findings. Verdict "Looks good" with the summary and "0 issues in 12 files"; never an empty card.
- Hundreds of findings. Groups show the first 5 per group then "and 41 more"; Nit and Info groups collapsed by default when > 20 findings total (proposed); list virtualised.
- Finding without a line (file- or PR-level): link shows the file only; PR-level shows "General".
- Line ranges.
src/auth.rs:142–150; ranges > 30 lines link to the start with a "30+ lines" tag. - Files not in the diff. Link opens the file at the line (host), tagged "outside this change".
- Fix touches several files. Preview shows per-file mini hunks and a combined
+a −r; Apply is atomic — all or none. - Agent proposes a fix in prose only. No Apply button; "Ask agent to apply" sends a steer.
- Duplicate findings across re-runs: matched by file + line + title hash (proposed); state carries over ("previously dismissed" tag) instead of reopening.
- Very fast reviews. Findings arriving inside
delay.row_guardrender without enter animation; verdict shows directly. - Very slow reviews. Streaming progress by files; stall thresholds from the status strip; partial findings are actionable before Done.
- Posting to a PR is outbound and visible to others: always
ConfirmPostwith the exact comments previewed; never auto-post, whatever the autonomy setting (family G). - Long titles / bodies. Title 1 line in compact, 2 lines in card; body 2 lines then "More"; code in bodies uses inline code styling and never wraps mid-token.
- RTL. Card mirrors; paths,
file:lineand code stay LTR in bidi isolates; severity glyph stays at inline-start. - Tiny sizes (16–20 px). Only the verdict glyph with a count (
⚠ 3); tooltip has the breakdown. - Dense IDE. Rows at 22 px, fix previews collapsed by default (expand with →).
- Touch. 44 px targets; swipe right = resolve, swipe left = dismiss (with undo toast); fix preview scrolls horizontally inside its frame.
- Offline. Apply / Post disabled-with-reason; dismiss / resolve queue locally and sync later with a "pending" dot.
- Colour-blind. Severity always has glyph shape + text label; daltonized preset swaps danger/amber hues per file-edit-chip.md §8.
Notes for AI
- Import
ReviewCardfromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
ReviewCardElinoxyn_gpui. - Props to set first:
findings. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.