Primitive of the day · 2026-10-27

git-dash-c-relative-path-resolution

A relative path argument under `git -C $REPO` resolves against the -C directory, NOT the caller's cwd — `git -C <repo> worktree add ../worktrees/x` lands sibling to the repo root no matter where the agent runs from.

When this applies

Scripting worktree creation (or other git path-taking commands) from agents whose cwd is unpredictable.

Preconditions

• git -C in use with relative path arguments

Do this

Rely on -C-relative resolution deliberately (the ../worktrees default) or pass absolute paths; never assume caller-cwd resolution.

What you should see

Worktrees land in the intended sibling directory regardless of invocation cwd.

How it fails if ignored

Assuming cwd-relative behavior scatters worktrees across whatever directory the agent happened to be in.

Do not use when

Absolute paths (no resolution ambiguity).

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