Claude Squad Review, Commit, Push: The Complete Post-Agent Review Workflow

The agent finished its task — and now comes the most important step: confirming what it did.

This isn't unnecessary overhead. Agents sometimes do more than you asked, sometimes go in a direction different from what you expected, sometimes change something you didn't notice. The review step is your last line of defense in the human-agent workflow.

Claude Squad's design makes this flow smooth — no switching to a different terminal window, no running git diff manually. You can complete the entire review-to-push flow directly inside the TUI.

Review Workflow Overview

A complete review workflow has four steps:

1. View the diff: See what the agent changed in the TUI
2. Confirm it's good: Manually verify the changes are within expected scope
3. Checkout (optional): Save changes to the branch and pause the session
4. Push: Push the branch to GitHub and open a PR

Step 1: View the Diff

Select the session you want to review (using ↑/↓), then press tab to switch to diff mode.

The right preview area shows all changes in this session's git worktree relative to the original branch — in standard git diff format, added lines in green, deleted lines in red.

For long diffs, scroll with shift-↑ and shift-↓.

Things to Check During Review

Scope of changes: Did the agent modify files you didn't expect? If it was only supposed to change UserService.ts but also touched AuthController.ts, figure out why.

Balance of additions vs. deletions: If the agent deleted many lines without corresponding additions, make sure it's not "simplifying" logic you actually need to keep.

Tests updated: Did the agent update tests when it changed logic? Did it update all callers when it changed function signatures?

New dependencies introduced: Are there new imports? Do you accept these dependencies?

Step 2: If You Need to Add Corrections

If you find issues while reviewing the diff, press ↵ to attach to that session and give the agent additional instructions directly:

You used 'any' type on line 45 of UserService.ts.
Please replace it with proper type definitions.
You can reference the types in src/types/User.ts

After the agent makes corrections, ctrl-q back to the TUI and press tab to view the diff again.

Step 3: Checkout (Commit and Pause)

Once you've confirmed this session's changes look good, press c for checkout.

This operation does two things:

1. Commits all uncommitted changes in this session to its branch
2. Marks the session as "paused"

After checkout, the session's changes are safely stored on its branch — even if you delete the session later, the branch remains.

If you want the agent to continue working on this task later, press r to resume the session and it will continue from where it paused.

Step 4: Push to GitHub

Once confirmed, press s to push. Claude Squad will:

1. Ensure all changes are committed (auto-commits if not)
2. Push this session's branch to GitHub remote

After pushing, go to GitHub and open a PR. Each session corresponds to a branch, each branch gets one PR — clean, trackable, and straightforward to review.

Alternative: Using git Commands Directly

If you prefer using git commands directly, that works too. Claude Squad's worktrees are standard git branches that can be operated with any git tool:

# Navigate to that worktree directory
cd ~/projects/my-app--claude-squad-1
 
# View changes
git diff HEAD
 
# Manually commit
git add .
git commit -m "feat: add UserService unit tests"
 
# Push
git push -u origin $(git branch --show-current)

This is equivalent to pressing s in the TUI — just manual.

Common Questions

Q: Push shows gh: command not found

gh CLI isn't installed or not in PATH. Go back to the installation article for prerequisite setup.

Q: Can't see the branch after pushing

Check your git remote configuration with git remote -v to confirm you have an origin set up.

Q: I'm not happy with what the agent did — how do I throw it all away?

Press D in the TUI to delete that session — the corresponding worktree gets cleaned up and the changes won't affect your main branch. This is the benefit of worktree isolation: the cost of abandoning is nearly zero.

With the complete review workflow mastered, the final article brings everything together — three real development task types and the best Claude Squad strategy for each.

Previous: Configuration and Profiles: Let Claude Squad Remember Your Tool Preferences Next: Real-World Scenarios: Three Development Task Types × Best Claude Squad Strategies