worktree-sweep

Find and remove stale git worktrees, then report reclaimed space.

Operates in report → confirm → execute order. Nothing is removed until the user approves the plan. After approval, perform the removals autonomously. Choices are gathered through interactive questions, not flags.

Step 0: Determine the scan scope (never hardcode paths)

Resolve where to look, in this priority order:

1. A path passed in $ARGUMENTS — use it verbatim as the scan root.
2. Otherwise, if the current working directory is inside a git repository, ask the user (interactive question) which scope to use:
   • this repository only — the repo the current directory belongs to;
   • all repositories under the clone root — find the hosting root by walking up to the common ancestor that contains many <owner>/<repo> directories, and show the resolved root in the question so the user can confirm or correct it.
3. If the current directory is not inside a repository and no path was given — ask the user for the directory to scan. Do not assume a default like ~/git.

For multi-repo scope, enumerate repositories by locating each .git directory (a directory, not a gitdir file) under the resolved root.

Step 1: Enumerate worktrees

For each in-scope repository:

git -C "$REPO" worktree list --porcelain

The first entry is the main checkout — never a removal candidate. Every additional entry is a candidate. Also note the current worktree (the one this session runs in, if any) and exclude it.

Step 2: Classify each candidate

For every candidate worktree path $WT:

• Dirty — uncommitted or untracked changes:

  git -C "$WT" status --porcelain
  

  A non-empty result means dirty. Inspect what changed before judging (see Step 4).

• Locked — git worktree list --porcelain prints a locked line. Read the lock reason. If it embeds a PID (e.g. pid 29180), check whether that process is still alive:

  ps -p "$PID" >/dev/null 2>&1 && echo live || echo stale