claude-worktree

Automate git worktree creation and configuration from active plans or branches.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill claude-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-worktree
Source: https://github.com/erclx/aitk/tree/main/claude/skills/claude-worktree
Command: npx skills add https://github.com/erclx/aitk --skill claude-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual friction of setting up and naming git worktrees, ensuring that your development environment remains clean and synchronized with your active plans or branches.

Core Features & Use Cases

  • Automated Naming: Derives worktree names from active plans or branch slugs to maintain consistent project structure.
  • Environment Repair: Automatically detects and fixes git configuration issues like incorrect core.bare settings that often occur when switching between worktrees.
  • Use Case: When you are ready to start a new feature, use this skill to instantly create a dedicated worktree directory that matches your current plan, preventing branch collisions and configuration drift.

Quick Start

Ask the assistant to enter a worktree for the current feature plan to automatically initialize the directory and configure the git environment.

Frequently Asked Questions about claude-worktree

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

FAQPage Schema
How do I automate git worktree creation for a new feature branch?

Automating git worktree creation involves deriving directory names from active project plans or branch slugs to instantly initialize a dedicated environment. This prevents branch collisions and maintains consistent project structure without manual directory setup.

Why does my git configuration break when switching between worktrees?

Git configuration breaks during worktree switches due to incorrect core.bare settings causing repository state drift. Repairing shared configuration flags and aligning branch names automatically resolves these environment issues for seamless context switching.

Do I need git CLI access to manage worktree lifecycle and repository state?

Git CLI access is required to manage the worktree lifecycle and perform repository state validation. The automation relies entirely on the local git command line interface to configure environments and repair configuration drift.

What is the best way to prevent branch collisions when starting multiple features?

The best way to prevent branch collisions is creating dedicated worktree directories that match your current plan. Deriving worktree names from active plans or branch slugs ensures consistent project structure and isolates development contexts.

Can I synchronize my development environment with active plans using git worktrees?

You can synchronize your development environment with active plans by deriving worktree names from branch slugs. This ensures your working directory remains clean, synchronized, and correctly configured for the specific feature plan.