Review UI

How to use the browser-based review interface.

Overview

When you run corg review, your browser opens to a local review UI. The interface has three main areas: a file tree on the left, the diff viewer in the center, and a review summary panel at the bottom.

File tree

  • Lists all changed files in the commit range
  • File status indicators: added, modified, deleted, renamed
  • Comment count badges show how many comments each file has
  • Click a file to navigate to its diff
  • Resizable width via drag handle (15–40% of the viewport, default 20%)
  • Width preference persists across sessions

Diff viewer

CorgReview supports two diff view modes:

Mode Description
UnifiedTraditional unified diff format (default)
SplitGitHub-style side-by-side view with aligned columns

Toggle between modes using the Unified/Split buttons in the diff header. Your preference persists across sessions.

Features

  • Syntax highlighting via Shiki (VS Code grammar support)
  • Line-by-line display with additions, deletions, and context
  • Hunk headers showing line ranges
  • Click the "+" button on any line to add a comment
  • Split view aligns deletions with corresponding additions

Comments

Click any line in the diff to add a comment. Each comment has a type that signals its importance to your AI agent.

Type Purpose
BlockerMust be addressed before approval
QuestionSeeking clarification
SuggestionImprovement idea (non-blocking)
NoteGeneral observation

Comment scopes

  • Line comments — Anchored to a specific line in a file
  • File comments — Apply to an entire file
  • General comments — Not tied to a specific file

All comments can be edited or deleted before submitting the review.

Review summary panel

  • Resizable — drag the handle between the diff viewer and the summary panel
  • Default split: 75% diff / 25% summary
  • Collapse or expand with the chevron toggle in the panel header
  • Free-form text area for your overall review feedback
  • Panel sizes persist across sessions

Review status

Before submitting, set your review status:

Status Meaning
ApproveChanges are acceptable
Request ChangesBlockers or issues must be addressed
CommentFeedback only, no approval decision

Submitting a review

Click "Submit Review" to finalize. CorgReview:

  1. Validates required fields
  2. Generates a markdown file with all comments, your summary, and the review status
  3. Saves it to .corg/reviews/
  4. Returns control to the CLI or MCP caller

The review file is human-readable markdown and can be committed to your repo as an audit trail.

Themes

CorgReview supports light and dark themes. Switch via the theme toggle in the UI. Your preference persists across sessions and applies to diffs, comments, and the entire interface.