git-wt

name	git-wt
description	Use the `git-wt` CLI to manage Git worktrees in the bare repository layout. Load when a task mentions `git wt`, `git-wt`, creating/removing/switching worktrees, or when the repository has a `.bare` directory with a `.git` file pointing to it.

git-wt

Use this skill when the user asks to manage Git worktrees with git-wt or when a repository uses the bare worktree layout: Git data lives in .bare, .git is a file pointing at ./.bare, and branch worktrees are sibling directories.

Detecting git-wt repositories

• From any directory in the repo, run:

  git rev-parse --git-common-dir
  

  If the result ends in .bare, treat the repo as a git-wt bare worktree layout.

• If you are at a repository root, a .git file containing gitdir: ./.bare and a .bare directory are also strong signals.

• If uncertain, run:

  git wt doctor
  

Operating rules for agents

• Prefer git wt (or git-wt) over raw git worktree commands in a git-wt layout so path resolution, fetching, branch cleanup, and safety prompts stay consistent.
• Prefer explicit, non-interactive commands. Avoid bare git wt add, git wt remove, and git wt switch in automation because they may open fzf pickers or prompts.
• git wt add prints the absolute created worktree path on stdout. Capture that path if you need to cd into the new worktree. Human progress and prompts are written to stderr.
• Use dry-runs before destructive cleanup. Only delete remote branches when the user explicitly asks for remote deletion.
• DEBUG=1 before a mutating command prints the underlying git operations instead of executing them.

Common commands

Inspect repository health and worktrees:

git wt doctor
git wt status
git wt list
git wt list --porcelain

Clone or migrate repositories:

git wt clone <url> [folder]
git wt migrate --dry-run
git wt migrate

Create worktrees with explicit arguments:

git wt add feature origin/feature
git wt add -b new-feature new-feature
git wt add --detach hotfix HEAD~5

Update the default branch worktree:

git wt update

Switch worktrees:

• For an interactive human workflow, use:

  cd "$(git wt switch)"
  

• For an agent workflow, inspect git wt list output and cd to the exact worktree path instead of invoking the interactive switch picker.

Remove worktrees safely:

git wt remove feature --dry-run
printf 'y\n' | git wt remove feature
git wt remove --sweep --dry-run
printf 'cleanup\n' | git wt remove --sweep

Remote branch deletion is destructive. Use it only when explicitly requested, and confirm with the branch name expected by the prompt:

git wt remove feature --delete-remote --dry-run
printf 'feature\n' | git wt remove feature --delete-remote

Suggested workflow

1. Inspect first with git wt doctor, git wt status, or git wt list.
2. Explain the planned operation when it will create, remove, or migrate worktrees.
3. Prefer a dry-run or DEBUG=1 preview where available.
4. Execute the explicit git wt command.
5. Report created paths, removed branches, and any follow-up command the user should run.