Pull requests and review

Superconductor tracks the active worktree, its branch, its target branch, and its pull request state. These surfaces drive prompting, checks, PR creation, merge preparation, and discard flows.

Review starts with the worktree

Open the worktree that holds the task you want to review. Superconductor compares that worktree against its target branch and lists the changed files.

Before reviewing, confirm:

• The worktree sits on the expected branch.
• The target branch matches the branch you intend to merge into.
• The diff contains the task changes.
• Generated files and lockfiles look expected.

Inspect the same state from a Superconductor-launched terminal:

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

Target branch matters

The target branch controls the comparison behind review summaries and checklists.

Change the target branch only when you mean to change the merge target:

sc worktree set-target-branch release/2026-05

Read the live value from Superconductor worktree status; do not infer it from the current branch name or from origin/HEAD.

Pull request awareness

When a branch has an associated pull request, Superconductor surfaces PR state alongside the worktree. The active worktree polls its provider directly. Inactive worktrees rely on cached or batch-refreshed PR and MR context, which keeps background traffic low.

PR state can show whether:

• The branch already has a PR.
• The PR target branch matches the worktree target.
• Checks or PR status changed after the last push.
• Cached PR context is ready when you return to an inactive worktree.

Action prompts

Workspace and project settings configure prompts and routing for these review-related actions:

• Create PR.
• Inline commit.
• Commit & push.
• Fix CI.
• Fix blocked merge.
• Fix comments.
• Fix changes.
• Resolve conflicts.
• Review.

Settings can differ by workspace. One workspace can pin different Create PR instructions or labels than another.

Reviewing agent work

A review loop includes:

1. Read the changed-file list.
2. Check the diff for correctness, tests, and user-facing behavior.
3. Run verification commands in the worktree terminal.
4. Prompt the agent with fixes.
5. Commit, push, open a PR, merge, or discard the worktree changes.

For agent follow-ups, name the specific change you want:

The diff changes the settings migration and the UI, but it does not update the docs page. Add the docs update only; do not touch the migration again.

Review units

Superconductor shows review state per branch-backed worktree. Standard Git workflows can split or move changes before you open a PR.