Wt Switch Create
Skill Verified ActiveCreate a new worktrunk worktree (optionally in another repo) and switch this session's working directory into it. Use when launching a session that should work in its own worktree (e.g. `/wt-switch-create my-branch -- <task>`, or `/wt-switch-create my-branch ~/workspace/other-repo -- <task>`), or mid-session to move work into a fresh branch.
Streamline the process of creating and switching to dedicated git worktrees for AI agents or individual tasks, ensuring a clean and isolated working environment.
Features
- Create new git worktrees
- Switch session working directory to a worktree
- Optionally specify a different repository for the worktree
- Execute tasks within the newly created worktree
- Idempotent worktree creation/switching
Use Cases
- Launching a new session that should operate in its own isolated worktree
- Mid-session, moving work into a fresh branch and worktree
- Parallelizing AI agent tasks by assigning each to a dedicated worktree
- Setting up isolated environments for specific development tasks
Non-Goals
- Managing the lifecycle of branches independently of worktrees
- Performing git operations like commit, push, or merge without explicit user permission
- Automatically removing worktrees with uncommitted changes
- Handling general git repository management beyond worktree operations
Prerequisites
- Requires the `wt` CLI (https://worktrunk.dev)
- Requires this plugin's WorktreeCreate hook
Installation
First, add the marketplace
/plugin marketplace add max-sixty/worktrunk/plugin install worktrunk@worktrunkQuality Score
VerifiedTrust Signals
Similar Extensions
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
Github
100Use gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Telegram Crabbox E2e Proof
100Use when reviewing, reproducing, or proving OpenClaw Telegram behavior with a real Telegram user on Crabbox, including PR review workflows that need an agent-controlled Telegram Desktop recording, TDLib user-driver commands, Convex-leased credentials, WebVNC observation, and motion-trimmed artifacts.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.