git-wt
Fast git worktree manager. Use when the user wants to create, list, switch between, or clean up git worktrees. Handles parallel development workflows, agent isolation, and multi-branch work.
Best use case
git-wt is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Fast git worktree manager. Use when the user wants to create, list, switch between, or clean up git worktrees. Handles parallel development workflows, agent isolation, and multi-branch work.
Teams using git-wt should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-wt/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git-wt Compares
| Feature / Agent | git-wt | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Fast git worktree manager. Use when the user wants to create, list, switch between, or clean up git worktrees. Handles parallel development workflows, agent isolation, and multi-branch work.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# git-wt — Git Worktree Manager `git-wt` manages isolated git worktrees stored globally at `~/.git-wt/<repo>/<name>/`. Worktrees live outside the repo — no `.gitignore` changes needed. ## Prerequisites `git-wt` must be installed and in PATH. Verify with `git wt --version`. If not installed, ask the user to install it themselves. ## Commands Reference ### Create a worktree ```bash git wt new # Auto-named; .env* + AI sessions copied by default git wt new my-feature # Named git wt new -b main hotfix # Fork from specific branch git wt new --no-copy-env experiment # Opt out of .env* copy git wt new --no-copy-ai scratch # Opt out of AI session copy/save git wt new --no-branch scratch # Detached HEAD (no branch created) ``` ### Check out an existing branch ```bash git wt checkout feature/login # Local branch → worktree (.env* + AI copied by default) git wt checkout origin/fix/bug-42 # Remote → local tracking branch → worktree git wt checkout fix/bug-42 # Auto-detects from remote git wt checkout feature/login my-fix # Custom worktree name git wt checkout --no-copy-env feature/api # Opt out of .env* copy ``` ### Navigate to a worktree ```bash cd $(git wt path <name>) # Jump into worktree git wt open <name> # Open in Cursor/VS Code/$EDITOR ``` ### List worktrees ```bash git wt list # Worktrees for current repo (managed + external) git wt list-all # Managed worktrees across ALL repos ``` External worktrees (created via `git worktree add`) appear with `[external]` tag. ### Adopt an external worktree ```bash git wt adopt my-hotfix # Adopt by name from list git wt adopt ../my-hotfix # Adopt by path (name = basename) git wt adopt /tmp/wt/fix fix-login # Adopt with custom name ``` Moves an external worktree under `~/.git-wt/` management. ### Find the main repo ```bash git wt origin # Print main repo path (from any worktree) ``` ### Remove worktrees ```bash git wt rm <name> # Remove managed worktree + delete its branch git wt clean # Remove all managed worktrees for current repo ``` `rm` only works on managed worktrees (under `~/.git-wt/`). For external worktrees, run `git wt adopt` first. ## Key Details - **Storage**: `~/.git-wt/<repo>/<name>/` — outside the repo, globally managed - **Branches**: prefixed `wt/` by default (e.g., `wt/my-feature`) - **Naming**: auto-generates `adjective-noun` names if no name given - **`rm`**: only works on managed worktrees — removes directory and deletes its branch - **`adopt`**: moves an external worktree under `~/.git-wt/` so git-wt fully manages it - **External worktrees**: `list`, `path`, `open` work with worktrees created outside git-wt - **`checkout`**: checks out an existing branch (local or remote) into a managed worktree — does NOT create new branches - **`.env*` copy**: enabled by default — copies `.env*` files from repo root into the new worktree directory (local filesystem only). Disable with `--no-copy-env` per run or `GIT_WT_COPY_ENV=false`. - **AI session preservation**: enabled by default. On create: copies AI config files and seeds origin's Claude + Codex sessions into the worktree (history visible in `/resume` and `codex resume` there). On rm: merges wt's Claude sessions back to origin (wt continuations win), discards seeded Codex copies, rebinds genuine wt-created Codex sessions to origin, syncs settings back. Local filesystem only. Disable with `--no-copy-ai` per run or `GIT_WT_COPY_AI=false`. - **`origin`**: prints main repo path — works from any worktree or main repo itself ## Environment Variables - `GIT_WT_HOME` — Root directory for all worktrees (default: `~/.git-wt`) - `GIT_WT_PREFIX` — Branch name prefix (default: `wt`) - `GIT_WT_COPY_ENV` — Copy `.env*` files on new (default: `true`) - `GIT_WT_COPY_AI` — Copy AI configs on new, save sessions on rm (default: `true`) - `GIT_WT_AI_PROVIDERS` — Space-separated AI providers to manage (default: `claude codex`) ## When to Use Use `git wt new` when: - Working on a separate task that needs isolation from current work - Running parallel agents that each need their own repo copy - Experimenting without affecting the current branch - Needing to quickly switch context between features Defaults you get for free (no flags): - `.env*` files from the repo root are copied into the worktree — dev servers that need env vars start immediately - `.claude/settings.local.json` (approved Claude commands) is copied into the worktree on create - On `new`, origin's Claude sessions are seeded into the worktree (cwd rewritten) and origin's Codex rollouts are duplicated with fresh UUIDs/cwd — `/resume` and `codex resume` in the worktree pick up the same history - On `rm`, Claude session files are merged back to origin (newer wt continuations replace origin's version), the seeded Codex copies are discarded, and genuine worktree Codex sessions get their `cwd` rebound to origin Use `--no-copy-env` / `--no-copy-ai` (or set `GIT_WT_COPY_ENV=false` / `GIT_WT_COPY_AI=false`) when: - You want a fully clean worktree without env or AI config - You're in CI or a scripted context where these are noise Use `git wt checkout` when: - You need to work on an existing branch in an isolated worktree - You want to check out a remote branch without manually creating a tracking branch - You're reviewing someone else's PR branch in isolation Use `git wt adopt` when: - A worktree was created with `git worktree add` and you want git-wt to manage it - You want the worktree moved to `~/.git-wt/` for consistent management ## Shell Aliases Optional `aliases/git-wt.sh` provides shorter commands. Source it in `.bashrc`/`.zshrc`: | Alias | What it does | |-------|-------------| | `wtcd <name>` | `cd` into a worktree | | `wto` | `cd` to the origin (main) repo | | `wtn [name]` | Create worktree + `cd` into it | | `wtco <branch>` | Checkout existing branch + `cd` into it | | `wtls` / `wtla` | List / list-all | | `wtrm` / `wtopen` / `wtclean` / `wtpath` | Shorthand for corresponding commands | ## Security - All operations are **local filesystem only** — git-wt never makes network requests or sends data externally - `--copy-env` copies `.env*` files between local directories on the same machine (repo root → worktree) - `--copy-ai` copies AI config/session files between local directories on the same machine - No credentials, tokens, or secrets leave the local filesystem - Worktrees are stored under `~/.git-wt/` with standard filesystem permissions ## Workflow: Parallel Agent Isolation ```bash # Agent 1: create isolated worktree with AI config git wt new --copy-env --copy-ai task-auth # Agent 2: create another git wt new --copy-env --copy-ai task-api # Each agent works independently in their worktree cd $(git wt path task-auth) # When done — sessions merged into origin (/resume), settings synced back git wt rm task-auth git wt rm task-api ```
Related Skills
swe-cli-skills
Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms
PicoClaw Fleet
Orchestrate a fleet of remote PicoClaw workers over SSH for fast, ephemeral one-shot tasks.
VibeCollab — Setup Instructions for AI Assistants
You are helping a user set up VibeCollab in their project.
raycast-extension-docs
Guidance for building, debugging, and publishing Raycast extensions using the Raycast documentation set. Use when Codex needs to create or modify Raycast extensions (React/TypeScript/Node), consult Raycast API reference or UI components, build AI extensions, handle manifest/lifecycle/preferences, troubleshoot issues, or prepare/publish extensions to the Raycast Store or Teams.
evomap
Connect to the EvoMap collaborative evolution marketplace. Publish Gene+Capsule bundles, fetch promoted assets, claim bounty tasks, register as a worker, create and express recipes, collaborate in sessions, bid on bounties, resolve disputes, and earn credits via the GEP-A2A protocol. Use when the user mentions EvoMap, evolution assets, A2A protocol, capsule publishing, agent marketplace, worker pool, recipe, organism, session collaboration, or service marketplace.
maestro
Intelligent skill knowledge gateway. Routes tasks to the right knowledge without loading all skills into context. MUST be consulted before any coding task — call the search_skills MCP tool to retrieve relevant expertise from 100+ indexed skills covering Swift, SwiftUI, concurrency, testing, architecture, performance, and security.
opentui
Comprehensive OpenTUI skill for building terminal user interfaces. Covers the core imperative API, React reconciler, and Solid reconciler. Use for any TUI development task including components, layout, keyboard handling, animations, and testing.
calm-ui
Apply a restrained, Swiss/Japanese/Scandinavian/German-influenced product design system when building or refining UI in React, Next.js, TypeScript, and shadcn/ui. Use when the user asks to build, refine, critique, redesign, or review a page, screen, component, form, table, dashboard, layout, or other frontend interface, especially in projects using shadcn/ui. Do not use for marketing sites, landing pages, non-UI work, or requests for bold, playful, maximalist, or otherwise expressive aesthetics.
solid
Apply SOLID principles to write flexible, maintainable, and testable code. Use when designing classes, interfaces, and module boundaries. Covers Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion with practical TypeScript examples and detection heuristics.
netops-asset-manager
Manage IT infrastructure assets (routers, switches, servers, GPU clusters) through a Go + Vue 3 platform with real-time health probing, SSH remote control, configuration backup, bulk import, network topology visualization, and PM2 process management. Supports H3C, Huawei, Cisco, MikroTik, Ruijie, DCN, and Linux. Use when the user asks about IT asset management, network device operations, infrastructure monitoring, SSH device control, or development on this Go + Vue 3 platform.
Goal: Build an LLM-based RAG App
Here is the MVP Implementation Plan.
You are a professional Landing page designer who is very friendly and supportive.
Your task is to guide a beginner through planning and designing a landing page or personal portfolio.