Verified:GitHub

worktrees

Create, list, and clean up Git worktrees under .worktrees.

1|Updated Mar 24, 2026

Search Tags:#git #worktrees #naming-conventions #worktree-management #version-control #parallel-development #feature-branches

Ready to run

npx skills add https://github.com/matteobortolazzo/claude-tools --skill worktrees-matteobortolazzo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktrees
Source: https://github.com/matteobortolazzo/claude-tools/tree/main/ccflow/skills/worktrees
Command: npx skills add https://github.com/matteobortolazzo/claude-tools --skill worktrees-matteobortolazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git worktrees are essential for isolated parallel development, but managing multiple worktrees, naming conventions, and cleanup can be error-prone without a clear pattern.

Core Features & Use Cases

Structure guidelines: central main worktree stays read-only for reference; feature worktrees live under .worktrees and are independently usable.
Naming conventions: each worktree follows the ticket-id-short-description pattern to ensure traceability.
Lifecycle & workflows: create, list, and clean up worktrees across features without disrupting the main branch.

Quick Start

Create a new feature worktree under .worktrees using the ticket-id and short description.

Frequently Asked Questions about worktrees

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

FAQPage Schema

How do I manage Git worktrees for parallel feature development?▼

To manage Git worktrees for parallel feature development, you can create isolated worktrees under a central .worktrees directory. This keeps your main branch read-only for reference while allowing independent work on multiple feature branches.

What is the best way to name Git worktrees for feature branches?▼

The best way to name Git worktrees is using the ticket-id-short-description pattern. This naming convention ensures traceability and links each isolated worktree directly to its corresponding development task.

How do I clean up Git worktrees without disrupting the main branch?▼

You can clean up Git worktrees without disrupting the main branch by removing feature worktrees located under the .worktrees directory. This preserves the central main worktree for ongoing reference.

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

You need to use Git worktrees when you require isolated parallel development across multiple feature branches. They allow you to work on different features simultaneously without switching branches or disrupting your main worktree.

Can I list all active Git worktrees across different feature branches?▼

Yes, you can list all active Git worktrees across different feature branches. This allows you to track ongoing parallel development and identify which worktrees require cleanup or further feature work.

Does Git worktree management require a specific directory structure?▼

Git worktree management benefits from a specific structure where the central main worktree stays read-only for reference. Feature worktrees are created under a .worktrees directory to keep parallel development isolated and organized.