Review changes

The review flow keeps code inspection, app-managed comment threads, agent follow-up, and Git state attached to the active worktree. Review before you commit, push, merge, clean up, or discard the branch.

Define the comparison

Confirm the branch and target before reading the diff. The target should be the branch into which this work will merge. A stale or incorrect target can make valid work look missing or unrelated changes look new.

The right panel and diff view show changed files, per-file status, additions and deletions, and anchored review threads. For a machine-readable check, run:

Copy

sc worktree status --json
sc worktree diff-summary --json
sc worktree review-checklist --json

Open the review surfaces

The right-panel Files tab lists changed files, per-file status, additions, and deletions. Select a file to open its comparison in the main diff view. The right-panel Review tab gathers line and file threads, their current states, and the controls for submitting pending findings.

Add review comments

Select a line range in the diff and add a comment. Use a file-level comment when the finding concerns the module or change as a whole rather than one line.

Comments remain app-managed state attached to the worktree. They can be open, pending, marked for a fix, or resolved. Replies stay in the same thread so the original finding and the agent’s response remain together.

For CLI-driven review, use the documented commands rather than storing guessed thread state in a file:

Copy

sc worktree review-list --json
sc worktree review-get "$COMMENT_ID" --json
sc worktree review-add --file src/auth.ts --start-line 41 --end-line 46 \
  --author "Local review" "Handle the expired-token path." --json

Triage AI findings

AI-generated review findings wait for your decision:

• Should fix moves a finding into the pending review set that can be sent to an agent.
• Dismiss resolves a finding that is incorrect, irrelevant, duplicated, or intentionally deferred.

Read the referenced code before choosing. Dismissing a finding changes its review state; it does not change the code.

Send pending comments to an agent

The review toolbar bundles pending threads and offers three destinations:

• Current chat stages the review bundle in the active agent conversation.
• Open in new chat starts a separate Chat UI session with the selected provider.
• Run in background dispatches the bundle without taking over the current tab.

The last destination can become the default for the next submission. Background review dispatch is separate from general app-managed agent orchestration and still requires you to choose the review destination explicitly.

An agent response can add replies to several threads. Review those replies and the changed code before resolving anything. Through the CLI, reply and resolve explicitly:

Copy

sc worktree review-reply "$COMMENT_ID" --provider codex \
  --resolve "Fixed and verified." --json

Use sc worktree review-set-status when the requested change concerns only the thread state.

Read forge checks

The app exposes current PR or MR checks through:

Copy

sc worktree checks --json

This refreshes missing check detail through the app’s forge integration before returning. Failed, pending, or completed checks also contribute to the adaptive Git action shown for the worktree.

Choose the next Git action

When the review is clean, the adaptive Git button can commit, push, create a PR or MR, surface review blockers, merge, and clean up the worktree. See Git actions and pull requests for state priority, dropdown choices, click behavior, and agent routing.

To discard the work, delete the task worktree only after confirming that you no longer need its uncommitted files, local-only commits, review threads, or session history. See Worktree cleanup before using a forced deletion.