Worktree

Create a feature worktree, sync its shared config with the bundled script, and
verify the result. The scripts this skill needs are bundled under its own
scripts/ directory, so it works without any pre-installed tooling.

Below, <skill-dir> is this skill's base directory — the absolute path announced
when the skill loads. Run the commands from inside the target git repository
(the creator resolves the repo from the current directory).

Steps

1. Create the worktree

Always call the bundled creator by its path — it works regardless of PATH and
needs nothing installed. It creates a new branch in its own worktree at
<parent>/<repo>.worktrees/<safe-branch> — create-only (never checks out an
existing branch), local refs only, base defaults to HEAD. The new branch has
no upstream, even from a remote base such as origin/trunk, so a plain first
git push cannot target the base branch.

"<skill-dir>/scripts/git-worktree-create" <branch> [<base-branch>]
# e.g. "<skill-dir>/scripts/git-worktree-create" feature/new-api origin/trunk

Do not branch on whether gitwt is installed: the gitwt global is only on
PATH in interactive shells, so that check is unreliable from an agent or a
non-interactive shell. gitwt is a human convenience for typing in a terminal
(see the install section); the bundled path is the canonical invocation here.

It prints the target directory and a cd line. Capture the target dir for step 2.

2. Sync shared config — never by hand

Run the bundled sync script against the new worktree path (this one works from any
directory). Do not replicate config by hand or hand-author symlinks — the
script owns that and is idempotent.

"<skill-dir>/scripts/ensure-shared-config-links.sh" "<worktree-path>"

By default, it resolves shared config from the conventional sibling
<repo>.config directory or from the repository's main worktree when the target
uses another layout. It links each eligible direct child into the worktree root
and is safe to re-run. See references/shared-config-links.md for explicit-path
usage and failure modes.

3. Verify the worktree is clean

git -C "<worktree-path>" status --short

Expect no output. If the sync script reports unignored shared-config links, add
the listed names to the exclude file it prints, then rerun the sync and status
commands. Do not start work while setup-owned entries remain in git status.

Global gitwt install (optional, one-time per machine)

To run the creator as a global gitwt command, symlink it to the stable
marketplace checkout of this skill (auto-updates when the skill republishes):

TARGET=~/.claude/plugins/marketplaces/dev-skills/worktree/scripts/git-worktree-create
test -x "$TARGET" || { echo "dev-skills not synced yet — run: git -C ~/.claude/plugins/marketplaces/dev-skills pull"; }
mkdir -p ~/bin
ln -sf "$TARGET" ~/bin/gitwt   # ensure ~/bin is on PATH

gitwt is an external shell command, so it only needs a stable on-disk path —
the marketplace checkout (fixed path, auto-updating), not the SHA-versioned
plugin cache (…/cache/dev-skills/dev-skills/<sha>/, which rotates per publish
and must never be a symlink target).