Worktree

Steps (follow strictly)

1. Validate arguments

args

2. Get repository information

# Get the repository root
git rev-parse --show-toplevel

# Get the repository name (directory name)
basename "$(git rev-parse --show-toplevel)"

3. Compute the slug

• Replace

  /

  with

  -

• Replace other special characters (spaces,

  :

  , etc.) with

  -

feature/add-button

feature-add-button

4. Determine the worktree path

{repo_root}/../{repo_name}.worktrees/{slug}

/home/user/my-project

/home/user/my-project.worktrees/feature-add-button

5. Check branch existence and create the worktree

# Check if branch exists locally
git branch --list "{branch_name}"

# Check if branch exists on remote
git ls-remote --heads origin "{branch_name}"

git worktree add "{path}" -b "{branch}"

git fetch origin "{branch}" && git worktree add "{path}" --track -b "{branch}" "origin/{branch}"

git worktree add "{path}" "{branch}"

• Neither local nor remote: create a new branch with

  -b

• Remote only:

  git fetch

  first, then create as a tracking branch with

  --track -b

• Local exists: check out the existing branch without

  -b

  (regardless of remote state)

6. Report completion

Gotchas

• Worktree path already exists:

  git worktree add

  will fail. Confirm with the user before running

  rm -rf

  , or use a different slug.
• No need to get the repo name from remote URL:

  basename $(git rev-parse --show-toplevel)

  is sufficient.
• Use absolute paths, not relative: always pass absolute paths to

  git worktree add

  .

• git ls-remote

  is checked by output, not exit code: determine "branch does not exist on remote" by whether stdout is empty, not by the exit code.