worktree-create

Create a git worktree with base-branch detection and plan initialization.

Updated Feb 4, 2026

Search Tags:#automation #git #branching #worktree #parallel-work #feature-development

Ready to run

npx skills add https://github.com/cbemister/claude-code --skill worktree-create-cbemister

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree-create
Source: https://github.com/cbemister/claude-code/tree/main/.claude/skills/worktree-create
Command: npx skills add https://github.com/cbemister/claude-code --skill worktree-create-cbemister

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the creation of git worktrees for isolated feature development and enables automatic plan initialization associated with the new worktree.

Core Features & Use Cases

Automatic creation of a new worktree aligned with a feature plan directory.
Base-branch detection with optional explicit base-branch input.
Automatic plan initialization under plans/active/<feature-name> to track progress and decisions.

Quick Start

Use the /worktree-create command to establish a new worktree and initialize its plan.

Usage: /worktree-create <feature-name> [base-branch]
Example: /worktree-create user-authentication
If base-branch is omitted, the tool will detect main or master as the default base.

Frequently Asked Questions about worktree-create

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

FAQPage Schema

How do I create a git worktree for isolated feature development?▼

To create a git worktree for isolated feature development, use an automated command that sets up the worktree and initializes a tracking plan. This enforces input validation, detects the base branch, and creates the initial plan file automatically.

Can I specify a base branch when setting up a git worktree for parallel work?▼

Yes, you can specify an explicit base branch when setting up a git worktree for parallel work. If the base branch is omitted, the tool automatically detects and defaults to either the main or master branch.

What is the best way to manage multi-branch experiments without git conflicts?▼

Using isolated git worktrees is the best way to manage multi-branch experiments without conflicts. This approach creates separate working directories for each branch, keeping parallel feature development completely separated.

How does automatic plan initialization work with new git worktrees?▼

Automatic plan initialization works with new git worktrees by creating a dedicated plan file under a specific active directory. This tracks progress and decisions linked directly to the newly created worktree for the feature.

Do I need to manually create a plan directory before creating a worktree?▼

No, you do not need to manually create a plan directory before creating a worktree. The automated workflow enforces input validation and handles the initial plan file creation under the active feature name directory automatically.

Why use isolated worktrees instead of standard git branching for feature development?▼

You should use isolated worktrees instead of standard git branching to maintain multiple working directories simultaneously. This allows parallel feature work and multi-branch experiments without stashing changes or switching branches repeatedly.