Git Worktree Manager
Manages multiple Git branches simultaneously in isolated directories to eliminate stashing and context-switching overhead.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Interactive menu-driven interface and direct command parsing for flexible management
- Automated worktree creation from local, remote, or new branches using a standardized sibling directory pattern
- Safe cleanup of worktrees and metadata pruning to maintain repository health
- Detailed status reporting including branch names, short commit hashes, and active environment indicators
- Navigation assistance with copy-ready commands for switching between isolated development environments
Use cases
- Running and testing multiple versions of a project concurrently
- Reviewing a pull request in a separate environment while keeping your main workspace intact
- Switching to a critical bug fix branch without stashing current feature progress
FAQ
What specific Git capabilities does it provide?
The skill provides a hybrid interface (interactive menu or direct commands) to create worktrees from local, remote, or new branches, list active worktrees with commit details, and generate copy-ready navigation commands for terminal switching.
How does this skill improve my development workflow?
It eliminates context-switching overhead by using a standardized sibling directory pattern (../project-branch). This keeps your IDE environments separate and ready to use, allowing you to move between tasks in seconds rather than minutes.
What does the Git Worktree Manager skill do?
This skill automates the management of Git worktrees, allowing you to have multiple branches checked out in separate, isolated directories simultaneously. It handles everything from creation and status reporting to safe deletion and metadata pruning.
Is it easy to clean up worktrees once I'm finished?
Yes. The skill includes dedicated commands for safe worktree removal and metadata pruning. This ensures your development environment remains clean and free of stale directory references once a branch is merged or abandoned.
When should I use this skill instead of standard git checkout?
Use this skill when you need to work on a new feature or urgent bug fix while keeping your current progress intact. It is ideal for parallel development and code reviews where you want to avoid the overhead of stashing, popping, and rebuilding environments.
Related skills
PDF Report Generator
Generates professional, distribution-ready PDF documents featuring advanced layouts, data visualizations, and custom branding.
Productivity Workflow29712 ptsSpreadsheet Generator
Generates professional Excel spreadsheets featuring structured data, complex formulas, dynamic charts, and professional formatting.
Productivity Workflow29712 ptsPrompt Optimizer
Transforms vague or incomplete requests into clear, actionable, and well-structured prompts using systematic analysis or guided interactive questionnaires.
Productivity Workflow11212 pts