Primitive of the day · 2026-10-29

worktree-detach-throwaway

For approaches you expect to discard, create the worktree with --detach (detached HEAD, no branch) — nothing to clean up branch-wise when the losing candidates are removed.

When this applies

The 'N approaches to the same problem' pattern where most worktrees will be thrown away.

Preconditions

• loss of the worktree's commits is acceptable

Do this

git worktree add --detach <path>; at teardown a simple remove suffices — no orphan branch is created.

What you should see

Zero branch-hygiene debt for discarded explorations.

How it fails if ignored

A 'throwaway' that turns out to be the winner requires git branch <name> <sha> before removal or the commits dangle.

Do not use when

Work that might be kept — you would have to rescue the commits from a detached HEAD.

Kind: tool-sequence. Part of the skill Git worktree for parallel agents. Free to reuse in your own agent skills.