worktree

Manage Git worktrees for parallel development across multiple branches.

2|3|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/psd401/psd-claude-plugins --skill worktree-psd401
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/psd401/psd-claude-plugins/tree/main/plugins/psd-coding-system/skills/worktree
Command: npx skills add https://github.com/psd401/psd-claude-plugins --skill worktree-psd401

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines parallel development by enabling you to manage multiple Git worktrees, allowing simultaneous work on different branches without context switching or stashing.

Core Features & Use Cases

  • Create Worktrees: Easily create new worktrees for specific branches or issue numbers.
  • List Worktrees: View all active worktrees and their associated branches.
  • Remove Worktrees: Safely remove worktrees, with warnings for uncommitted changes.
  • Prune Stale Worktrees: Clean up any unlinked worktree directories.
  • Use Case: Switch between developing a new feature, fixing a bug on a release branch, and experimenting with a refactor, all within separate, independent worktree checkouts.

Quick Start

Use the worktree skill to create a new worktree for the branch named 'feature/new-login-flow'.

Frequently Asked Questions about worktree

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

FAQPage Schema
How do I manage git worktrees for parallel development without stashing changes?

Git worktrees allow simultaneous work on multiple branches by creating independent working directories, eliminating context switching and stashing. You can create, list, remove, and prune worktrees to manage parallel feature development, bug fixes, and experiments efficiently.

What is the best way to create a git worktree from an issue number?

Creating a git worktree from an issue number automatically generates a corresponding branch name. This feature integrates with GitHub CLI to streamline parallel development, allowing you to quickly spin up isolated working directories for specific issues.

Do I need GitHub CLI to manage git worktrees?

GitHub CLI is required for this worktree management approach. It provides the repository operations and issue number integration needed to automatically name branches and manage parallel development workflows alongside standard Git functionality.

Can I safely remove a git worktree with uncommitted changes?

Removing git worktrees triggers warnings for uncommitted changes to prevent data loss. The management workflow includes safeguards that alert you before deleting directories, ensuring parallel development branches are protected during cleanup operations.

How do I clean up stale git worktrees that are no longer linked?

Pruning stale git worktrees cleans up unlinked worktree directories from your repository. This maintenance operation removes orphaned working directories, keeping your parallel development environment organized and preventing clutter from abandoned branch checkouts.