create-worktrees — Claude Code command: a worktree per open PR
Pulls every open pull request through GitHub CLI and sets up a separate git worktree for each branch under ./tree/. Useful when you want several PRs checked out at once without switching branches in the main checkout.
npx claude-code-templates@latest --command git-workflow/create-worktreesWhat create-worktrees does
The command runs gh pr list, reads the branch names and calls git worktree add for each one into ./tree/<BRANCH_NAME>. Branch names with slashes like feature/foo get nested directories, and existing worktrees are skipped instead of recreated. It finishes with git worktree list so you can see the result.
The same file carries a second script: it asks for a branch name, checks whether that branch already exists, then creates the branch and its worktree. You can point it at a different base than HEAD — a commit, tag or another branch. There is also an optional cleanup block that walks the worktrees and removes the ones whose branches are gone.
GitHub CLI has to be installed and authenticated first, since the command checks gh auth status and exits without a login. It only runs inside a git repository, and cleanup deletes with --force, so read the list before letting it run.
What it helps with
- check out a separate working copy for every open PR
- review several branches at once without touching the main checkout
- create a branch and get its worktree in one step
- remove worktrees whose branches were deleted
- branch off a specific commit or tag instead of HEAD
Example prompts for the agent
- create worktrees for all open PRs
- make a new branch feature/user-authentication with a worktree
- clean up worktrees for branches that no longer exist
How to install create-worktrees
1claude-code-templates
npx claude-code-templates@latest --command git-workflow/create-worktrees2Manually: put the files in place
.claude/commands/create-worktrees.mdCall it with /create-worktrees. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/create-worktrees.mdCall it with /prompts:create-worktrees. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/create-worktrees.prompt.mdManually: put the files in place
.gemini/commands/create-worktrees.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about create-worktrees
How do I install create-worktrees in Claude?
Through the templates CLI: npx claude-code-templates@latest --command git-workflow/create-worktrees. The command then lives at .claude/commands/create-worktrees.md.
What does create-worktrees do?
It lists open pull requests with GitHub CLI and creates one git worktree per branch under ./tree/. It can also spin up a brand new branch with its worktree and drop stale directories.
What do I need before running it?
An installed and authenticated GitHub CLI — without gh auth login the command stops at the first check. Run it from inside a git repository.
Source text
create-worktrees.md · MIT
---
description: "This command fetches all open pull requests using GitHub CLI, then creates a git worktree for each PR's branch in the ./tree/<BRANCH_NAME> directory."
---
# Git Worktree Commands
## Create Worktrees for All Open PRs
This command fetches all open pull requests using GitHub CLI, then creates a git worktree for each PR's branch in the `./tree/<BRANCH_NAME>` directory.
```bash
# Ensure GitHub CLI is installed and authenticated
gh auth status || (echo "Please run 'gh auth login' first" && exit 1)
# Create the tree directory if it doesn't exist
mkdir -p ./tree
# List all open PRs and create worktrees for each branch
gh pr list --json headRefName --jq '.[].headRefName' | while read branch; do
# Handle branch names with slashes (like "feature/foo")
branch_path="./tree/${branch}"
# For branches with slashes, create the directory structure
if [[ "$branch" == */* ]]; then
dir_path=$(dirname "$branch_path")
mkdir -p "$dir_path"
fi
# Check if worktree already exists
if [ ! -d "$branch_path" ]; then
echo "Creating worktree for $branch"
git worktree add "$branch_path" "$branch"
else
echo "Worktree for $branch already exists"
fi
done
# Display all created worktrees
echo "\nWorktree list:"
git worktree list
```
### Example Output
```
Creating worktree for fix-bug-123
HEAD is now at a1b2c3d Fix bug 123
Creating worktree for feature/new-feature
HEAD is now at e4f5g6h Add new feature
Worktree for documentation-update already exists
Worktree list:
/path/to/repo abc1234 [main]
/path/to/repo/tree/fix-bug-123 a1b2c3d [fix-bug-123]
/path/to/repo/tree/feature/new-feature e4f5g6h [feature/new-feature]
/path/to/repo/tree/documentation-update d5e6f7g [documentation-update]
```
### Cleanup Stale Worktrees (Optional)
You can add this to remove stale worktrees for branches that no longer exist:
```bash
# Get current branches
current_branches=$(git branch -a | grep -v HEAD | grep -v main | sed 's/^[ *]*//' | sed 's|remotes/origin/||' | sort | uniq)
# Get existing worktrees (excluding main worktree)
worktree_paths=$(git worktree list | tail -n +2 | awk '{print $1}')
for path in $worktree_paths; do
# Extract branch name from path
branch_name=$(basename "$path")
# Skip special cases
if [[ "$branch_name" == "main" ]]; then
continue
fi
# Check if branch still exists
if ! echo "$current_branches" | grep -q "^$branch_name$"; then
echo "Removing stale worktree for deleted branch: $branch_name"
git worktree remove --force "$path"
fi
done
```
## Create New Branch and Worktree
This interactive command creates a new git branch and sets up a worktree for it:
```bash
#!/bin/bash
# Ensure we're in a git repository
if ! git rev-parse --is-inside-work-tree > /dev/null 2>&1; then
echo "Error: Not in a git repository"
exit 1
fi
# Get the repository root
repo_root=$(git rev-parse --show-toplevel)
# Prompt for branch name
read -p "Enter new branch name: " branch_name
# Validate branch name (basic validation)
if [[ -z "$branch_name" ]]; then
echo "Error: Branch name cannot be empty"
exit 1
fi
if git show-ref --verify --quiet "refs/heads/$branch_name"; then
echo "Warning: Branch '$branch_name' already exists"
read -p "Do you want to use the existing branch? (y/n): " use_existing
if [[ "$use_existing" != "y" ]]; then
exit 1
fi
fi
# Create branch directory
branch_path="$repo_root/tree/$branch_name"
# Handle branch names with slashes (like "feature/foo")
if [[ "$branch_name" == */* ]]; then
dir_path=$(dirname "$branch_path")
mkdir -p "$dir_path"
fi
# Make sure parent directory exists
mkdir -p "$(dirname "$branch_path")"
# Check if a worktree already exists
if [ -d "$branch_path" ]; then
echo "Error: Worktree directory already exists: $branch_path"
exit 1
fi
# Create branch and worktree
if git show-ref --verify --quiet "refs/heads/$branch_name"; then
# Branch exists, create worktree
echo "Creating worktree for existing branch '$branch_name'..."
git worktree add "$branch_path" "$branch_name"
else
# Create new branch and worktree
echo "Creating new branch '$branch_name' and worktree..."
git worktree add -b "$branch_name" "$branch_path"
fi
echo "Success! New worktree created at: $branch_path"
echo "To start working on this branch, run: cd $branch_path"
```
### Example Usage
```
$ ./create-branch-worktree.sh
Enter new branch name: feature/user-authentication
Creating new branch 'feature/user-authentication' and worktree...
Preparing worktree (creating new branch 'feature/user-authentication')
HEAD is now at abc1234 Previous commit message
Success! New worktree created at: /path/to/repo/tree/feature/user-authentication
To start working on this branch, run: cd /path/to/repo/tree/feature/user-authentication
```
### Creating a New Branch from a Different Base
If you want to start your branch from a different base (not the current HEAD), you can modify the script:
```bash
read -p "Enter new branch name: " branch_name
read -p "Enter base branch/commit (default: HEAD): " base_commit
base_commit=${base_commit:-HEAD}
# Then use the specified base when creating the worktree
git worktree add -b "$branch_name" "$branch_path" "$base_commit"
```
This will allow you to specify any commit, tag, or branch name as the starting point for your new branch.
© davila7 · MIT · davila7/claude-code-templates