review-branch

Forge Review Branch

Review an unmerged branch holistically. Dispatches parallel review agents that examine the total diff (not commit-by-commit), check blast radius, verify conventions, and validate security — following Anthropic's multi-agent review architecture.

Usage

/forge review-branch [FLAGS]

Parse Arguments

Flag	Default	Description
--base BRANCH	main	Base branch to diff against
--head BRANCH	current HEAD	Branch to review (defaults to current branch)
--spec SPEC	(none)	Path to spec file for acceptance criteria verification
--depth quick|standard|thorough	standard	Review depth
--fix	(off)	Automatically fix CRITICAL issues found
--comment	(off)	Post results as GitHub PR comment via gh

Pre-flight Check

1. Verify this is a git repository. If not: Not a git repository.
2. Verify the base branch exists: git rev-parse --verify {base}. If not: Base branch '{base}' not found.
3. Verify there are changes to review: git diff --name-only {base}...{head}. If empty: No changes between {base} and {head}. Nothing to review.
4. Read .forge/capabilities.json if it exists (for tool-aware review).

Step 1: Gather Branch Context

Run these commands to understand the full scope of changes:

# Total diff stats
git diff --stat {base}...{head}

# All changed files
git diff --name-only {base}...{head}

# Commit log for the branch
git log --oneline {base}...{head}

# Number of commits
git rev-list --count {base}...{head}

Present a brief summary:

Forge Review Branch
===================================
Base:    {base}
Head:    {head}
Commits: {N}
Files:   {M} changed ({additions}+, {deletions}-)

Step 2: Convention Inference

Before reviewing, understand the codebase's conventions (same as forge-executor Step 4):

1. Check for CLAUDE.md, .editorconfig, linting config
2. If absent, auto-detect from existing code:
   • Import style (ESM vs CJS)
   • Naming conventions
   • Error handling patterns
   • Test framework and location
   • File organization
3. Store inferred conventions for use by review agents