← ClaudeAtlas

wt-helplisted

Answer common questions about working with worktrees — VSCode integration, gitignore, build artifacts, workflow tips. Use this when the user asks how worktrees work, why something looks different in their editor, how to see diffs, or has any question about the worktree setup. Also triggers for `/wt-help [topic]`.
ThinkVelta/agent-tracker · ★ 0 · Code & Development · score 78
Install: claude install-skill ThinkVelta/agent-tracker
# Worktree Help `$ARGUMENTS` is the user's question. If empty, print the **Overview** section below verbatim. Otherwise, answer their question using the **FAQ** section as your primary reference, falling back to your knowledge of git worktrees and this repo's setup. Keep answers concise and practical. When relevant, include `code .claude/worktrees/<branch-dir>` — it's the single most useful tip for new users. --- ## Overview (print when `$ARGUMENTS` is empty) The `/wt-*` skills are a thin wrapper around git worktrees that let you run multiple branches of this repo in parallel, each in its own isolated directory. **Why it exists.** Switching branches mid-task is disruptive: you stash, rebuild, lose state. Worktrees give each branch its own directory and its own SwiftPM build cache — so you (or a parallel Claude agent) can spin up a separate task without touching what you're already working on. The skills automate the lifecycle bookkeeping. ### Links - Git worktrees docs: https://git-scm.com/docs/git-worktree **Available `/wt-*` skills** | Command | Purpose | | ---------------------------------------------------- | ----------------------------------------------------------- | | `/wt-open [branch or description] [--base <branch>]` | Create or reopen a worktree (build warm-up included) | | `/wt-list [--stale]` | List active worktrees wi