Best use case
switch-worktree is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Switch the current session to work in an existing git worktree
Teams using switch-worktree 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/switch-worktree/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How switch-worktree Compares
| Feature / Agent | switch-worktree | 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?
Switch the current session to work in an existing git worktree
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.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# Switch to worktree Switch the current session to an existing worktree. ## Steps ### 1. Resolve the worktree If `$ARGUMENTS` is empty, list available worktrees and ask the user to pick one: ``` git worktree list ``` Otherwise, let `NAME` = `$ARGUMENTS`. The worktree path is `<repo-root>/.worktrees/<NAME>`. Verify the worktree exists in `git worktree list` output. If not, stop with an error. Let `WORKTREE` = the absolute path to the worktree. ### 2. Switch cwd ``` cd WORKTREE ``` Then verify the switch took effect: ``` pwd ``` If `pwd` does not show `WORKTREE`, stop with an error — the cwd did not persist. ### 3. Report ``` Switched to worktree: WORKTREE Branch: <current branch from git branch --show-current> ```
Related Skills
worktree-make-dev
Set up a dev environment in an existing worktree (make dev + copy secrets)
worktree-from-issue
Create a git worktree with a new branch for implementing a fix or feature for a GitHub issue
create-worktree
Create or reuse a git worktree for a pull request or branch so reviews and work happen in isolation
find-source
No description provided.
review-pr
Analyze a GitHub pull request including diff, comments, related issues, and local code context
release-notes
Generate release notes between two git tags with categorized PR summaries and author attribution
optimize-code
Analyze and optimize Python code performance in critical paths
implement-issue
Triage, plan, and implement a fix or feature for a GitHub issue end-to-end
dashboard
Use when reading, editing, or creating files in dlt/_workspace/helpers/dashboard/ or tests/workspace/helpers/dashboard/ or tests/e2e/
auto-write-test-rules
Use when adding or proposing a new test ONLY if the test rules are not present
auto-import-rules
Enforces dlt import conventions and ordering. Use when writing or modifying Python imports in dlt/ or tests/.
auto-docstring-rules
Enforces dlt docstring conventions. Use when writing or modifying docstrings, classes, or function signatures in Python files.