git-worktrees

Manage multiple Git worktrees for parallel development and context switching.

Updated Mar 10, 2026

Search Tags:#git #workflow #version control #worktrees #branching #parallel development

Ready to run

npx skills add https://github.com/Gamezar/opencode-cek --skill git-worktrees-gamezar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-worktrees
Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/git/skills/git-worktrees
Command: npx skills add https://github.com/Gamezar/opencode-cek --skill git-worktrees-gamezar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines parallel development by allowing you to work on multiple branches simultaneously without the overhead of stashing or cloning, enabling seamless context switching and isolated testing.

Core Features & Use Cases

Parallel Development: Maintain separate working directories for different branches.
Context Switching: Effortlessly move between tasks by changing directories, not branches.
PR Review: Review pull requests in isolation without disrupting your current work.
Use Case: You're working on a new feature, but a critical bug is reported. Create a new worktree for the hotfix branch, resolve the bug, and push it, all while keeping your feature work untouched in its own directory.

Quick Start

Use the git worktrees skill to create a new worktree for the 'develop' branch in the '../project-develop' directory.

Frequently Asked Questions about git-worktrees

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

FAQPage Schema

How do I work on multiple Git branches at the same time without stashing changes?▼

Git worktrees let you work on multiple branches simultaneously by maintaining separate working directories linked to a single repository, eliminating the overhead of stashing or cloning for seamless context switching.

What is the best way to review a pull request without disrupting my current feature development?▼

Reviewing pull requests in isolation is a core use case for Git worktrees. You can create a separate worktree for the PR branch, review it independently, and keep your current feature work untouched in its own directory.

Can I use Git worktrees to fix a critical bug while keeping my ongoing feature branch intact?▼

Yes, Git worktrees facilitate isolated bug fixing by allowing you to create a new working directory for the hotfix branch. You can resolve the bug and push it without affecting your untouched feature development directory.

How does parallel development with Git worktrees differ from cloning multiple repositories?▼

Git worktrees maintain separate working directories linked to a single repository rather than creating full clones. This enables efficient parallel development and context switching with significantly less overhead and storage.

When do I need to use Git worktrees for version control workflows?▼

You need Git worktrees when managing simultaneous feature development, isolated bug fixing, or side-by-side PR reviews. The technique allows effortless context switching between tasks by changing directories instead of branches.

Do I need any special dependencies to manage multiple Git worktrees for parallel development?▼

No special dependencies are required. The Skill leverages Git's native worktree functionality to manage parallel development and context switching directly within your existing version control environment.