worktree-switch

List and switch between Git worktrees for parallel development.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/mvillmow/ml-odyssey --skill worktree-switch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-switch
Source: https://github.com/mvillmow/ml-odyssey/tree/main/.claude/skills/worktree-switch
Command: npx skills add https://github.com/mvillmow/ml-odyssey --skill worktree-switch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? This Skill eliminates the need to stash or commit work when switching between different Git branches, allowing developers to work on multiple tasks in parallel without context-switching overhead. It automates the process of managing multiple work environments.

Core Features & Use Cases:

  • List Worktrees: Quickly view all active Git worktrees and their associated branches.
  • Efficient Switching: Change development contexts by simply changing directories, enabling rapid task switching.
  • Use Case: You're working on a feature, but a critical bug needs an immediate fix. Use this skill to switch to a bugfix worktree, address the bug, and then return to your feature without losing your current progress or needing to stash changes.

Quick Start: Use the worktree-switch skill to list all active git worktrees.

Frequently Asked Questions about worktree-switch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch between Git branches without stashing my work?

Git worktrees let you maintain multiple branch checkouts simultaneously in separate directories. Switch between them instantly without stashing or committing, keeping all work-in-progress changes isolated and accessible.

What's the best way to work on multiple Git branches in parallel?

Create separate Git worktrees for each branch or task. This approach eliminates context-switching overhead by letting you jump between directories instead of checking out and stashing repeatedly.

How do I list and navigate all my active Git worktrees?

Use the worktree-switch skill to list all active worktrees and their associated branches, then change directories to switch contexts. The skill provides shell aliases and scripting tools to automate listing and navigation.

Can I test multiple Git branches side-by-side without losing progress?

Yes. Git worktrees enable parallel development by maintaining separate checkouts of different branches. Compare implementations, test changes, and verify fixes across branches simultaneously without affecting your primary work environment.

Do I need special setup to use Git worktrees for development workflow?

Git worktrees require basic naming conventions and shell tooling. The worktree-switch skill includes a switch_worktree.sh script, shell aliases, and tmux guidance to list, navigate, verify, and manage worktrees efficiently.

What happens when I need to fix a critical bug while working on a feature?

Switch to a separate worktree for the bugfix without stashing your feature work. Complete the fix, then return to your feature worktree with all progress preserved and no manual recovery needed.