Arclabs Studio Arcknowledge Arc Worktrees Workflow

ARC Labs Studio - Git Worktrees Workflow

Overview

Git worktrees allow you to have multiple working directories from the same repository, each on a different branch. This enables true parallel development without stashing or switching branches.

Benefits

• Work on multiple features simultaneously
• Run tests in one worktree while coding in another
• Keep context separate per feature
• Run 3 Claude Code instances (one per worktree)
• No stashing, no branch switching

ARC Labs Directory Structure

~/Developer/ARCLabsStudio/Apps/
├── FavRes-iOS/                    # Main worktree (develop branch)
│   ├── .git/                      # Git directory (shared)
│   └── Tools/ARCDevTools/         # Submodule
│       └── ARCKnowledge/          # Nested submodule
│
└── FavRes-iOS-worktrees/          # Feature worktrees
    ├── FVRS-123/                  # Worktree for ticket FVRS-123
    │   └── Tools/ARCDevTools/     # Initialized submodules
    ├── FVRS-124/
    └── FVRS-125/

Instructions

Creating a New Worktree

Step 1: Create Branch and Worktree

From the main repository (FavRes-iOS):

# Navigate to main repo
cd ~/Developer/ARCLabsStudio/Apps/FavRes-iOS

# Fetch latest changes
git fetch origin

# Create worktree with new branch from develop
git worktree add \
  ../FavRes-iOS-worktrees/FVRS-123 \
  -b feature/FVRS-123-description \
  origin/develop

# Or from main (for hotfixes)
git worktree add \
  ../FavRes-iOS-worktrees/FVRS-123 \
  -b hotfix/FVRS-123-description \
  origin/main

Step 2: Initialize Submodules

Submodules are NOT automatically initialized in new worktrees:

# Navigate to new worktree
cd ../FavRes-iOS-worktrees/FVRS-123

# Initialize and update submodules recursively
git submodule update --init --recursive

# Verify submodules
git submodule status

Step 3: Open Claude Code

# Open Claude Code in the new worktree
claude

Managing Worktrees

# List all worktrees
git worktree list

# Quick status of all worktrees
for wt in ~/Developer/ARCLabsStudio/Apps/FavRes-iOS-worktrees/*/; do
  echo "=== $(basename $wt) ==="
  git -C "$wt" status -sb
done

Cleanup After PR Merge

# Navigate to main repo
cd ~/Developer/ARCLabsStudio/Apps/FavRes-iOS

# Remove worktree
git worktree remove ../FavRes-iOS-worktrees/FVRS-123

# Or force remove if there are untracked files
git worktree remove --force ../FavRes-iOS-worktrees/FVRS-123

# Delete local branch (if PR was merged)
git branch -d feature/FVRS-123

# Prune stale entries
git worktree prune

Shell Aliases for Quick Navigation

Add to ~/.zshrc:

# =============================================================================
# ARC Labs Worktrees Navigation
# =============================================================================

# Base paths
export ARC_APPS="$HOME/Developer/ARCLabsStudio/Apps"
export ARC_FAVRES="$ARC_APPS/FavRes-iOS"
export ARC_WORKTREES="$ARC_APPS/FavRes-iOS-worktrees"

# Quick navigation to main worktree
alias zf="cd $ARC_FAVRES && pwd"

# Quick navigation to worktrees (za, zb, zc pattern)
alias za="cd $ARC_WORKTREES/\$(ls $ARC_WORKTREES | head -1) 2>/dev/null && pwd || echo 'No worktrees'"
alias zb="cd $ARC_WORKTREES/\$(ls $ARC_WORKTREES | sed -n '2p') 2>/dev/null && pwd || echo 'No second worktree'"
alias zc="cd $ARC_WORKTREES/\$(ls $ARC_WORKTREES | sed -n '3p') 2>/dev/null && pwd || echo 'No third worktree'"

# Navigate to specific worktree by ticket ID
zw() {
  local ticket="$1"
  if [ -z "$ticket" ]; then
    echo "Usage: zw FVRS-123"
    echo "Available worktrees:"
    ls "$ARC_WORKTREES" 2>/dev/null || echo "No worktrees found"
    return 1
  fi

  local path="$ARC_WORKTREES/$ticket"
  if [ -d "$path" ]; then
    cd "$path" && pwd
  else
    echo "Worktree not found: $path"
    echo "Available: $(ls $ARC_WORKTREES 2>/dev/null | tr '\n' ' ')"
    return 1
  fi
}

# List all worktrees with status
zwl() {
  echo "=== FavRes Worktrees ==="
  git -C "$ARC_FAVRES" worktree list
}

# Create new worktree (from develop)
zwn() {
  local ticket="$1"
  local desc="$2"

  if [ -z "$ticket" ]; then
    echo "Usage: zwn FVRS-123 [description]"
    return 1
  fi

  local branch_name="feature/$ticket"
  if [ -n "$desc" ]; then
    branch_name="feature/$ticket-$(echo $desc | tr ' ' '-' | tr '[:upper:]' '[:lower:]')"
  fi

  cd "$ARC_FAVRES" || return 1
  git fetch origin

  git worktree add \
    "$ARC_WORKTREES/$ticket" \
    -b "$branch_name" \
    origin/develop

  if [ $? -eq 0 ]; then
    cd "$ARC_WORKTREES/$ticket"
    git submodule update --init --recursive
    echo ""
    echo "Worktree created: $ARC_WORKTREES/$ticket"
    echo "Branch: $branch_name"
    echo "Run 'claude' to start coding"
  fi
}

# Remove worktree after PR merge
zwr() {
  local ticket="$1"

  if [ -z "$ticket" ]; then
    echo "Usage: zwr FVRS-123"
    echo "Available worktrees:"
    ls "$ARC_WORKTREES" 2>/dev/null || echo "No worktrees found"
    return 1
  fi

  local path="$ARC_WORKTREES/$ticket"

  if [ ! -d "$path" ]; then
    echo "Worktree not found: $path"
    return 1
  fi

  echo "Removing worktree: $path"
  cd "$ARC_FAVRES" || return 1

  git worktree remove "$path" --force
  git worktree prune

  echo "Worktree removed"
  echo "Don't forget to delete the branch if PR was merged:"
  echo "   git branch -d feature/$ticket-*"
}

After adding, reload shell:

source ~/.zshrc

Linear Integration

Branch Naming Convention

Workflow with Linear

1. Get ticket from Linear (e.g., FVRS-123)
2. Create worktree: zwn FVRS-123 add-restaurant-search
3. Open Claude Code: claude
4. Code and commit: Follow conventional commits
5. Create PR: Link to Linear ticket
6. After merge: zwr FVRS-123

Best Practices

• Maximum 3 active worktrees (matches Ghostty tabs 1-3)
• Complete and clean up before creating new ones
• Keep develop branch clean - only merge via PR

Common Mistakes

Examples

Starting parallel development on two features

User says: "I need to work on FVRS-123 and FVRS-124 in parallel"

1. zwn FVRS-123 restaurant-search - creates first worktree
2. zwn FVRS-124 map-integration - creates second worktree
3. Open Ghostty tabs: Tab 1 = main, Tab 2 = FVRS-123, Tab 3 = FVRS-124
4. Run claude in each tab
5. Result: Three independent development environments

Cleaning up after feature merge

User says: "FVRS-123 was merged, clean up"

1. zwr FVRS-123 - removes worktree and prunes
2. git branch -d feature/FVRS-123-restaurant-search - deletes local branch
3. git push origin --delete feature/FVRS-123-restaurant-search - deletes remote
4. Result: Clean worktree state

Related Skills

Converted and distributed by TomeVault — claim your Tome and manage your conversions.