create-worktree

Included with Lifetime

$97 forever

Creates a new git worktree for parallel development. Use when the user wants to work on something in a separate worktree, start parallel work, or isolate changes.

General

What this skill does

# Create Worktree

Creates a git worktree so the user can work on a separate branch in parallel without disturbing their current working directory.

## Current State

Current directory:
!`pwd`

Current branch:
!`git branch --show-current`

Worktree list:
!`git worktree list`

Git root:
!`git rev-parse --show-toplevel`

Git common dir:
!`git rev-parse --git-common-dir`

## Workflow

### Step 1: Determine the Branch

**Check for project branch naming conventions** by scanning CLAUDE.md, CONTRIBUTING.md, or similar project docs for branch naming policies. If a convention exists, follow it. If not, use bare `<short-name>` without prefix segments (no `feat/`, `fix/`, etc.).

**Determine the branch based on current state:**

- **On `main`/`master`, or already in a worktree:** Infer the scope of work from conversation context or the provided argument. Create a new branch name from that. Do not ask the user unless the scope is genuinely unclear.
- **On a non-main branch, not in a worktree:** Ask the user:
1. Whether to move this branch to the worktree, or create a new branch
2. Whether to branch off the current branch or off main

If the user provided an argument, use it to determine or influence the branch name.

### Step 2: Determine the Worktree Location

Determine the parent directory for the worktree using the first matching condition:

- **If in the sibling worktree layout:** The worktree list (from Current State above) shows multiple worktrees sharing a common parent directory, or the current git root's basename matches the current branch (e.g., directory named `main` on branch `main`). Place the new worktree as a sibling in that parent directory.
- **If already in a linked worktree:** Place the new worktree in the same parent directory as the current worktree (a sibling directory).
- **If in the primary clone directory:** Place it at `<repo-parent>/worktrees/<dir-name>`, where `<repo-parent>` is the directory containing the repository root.

**Directory naming rules:**
- If the branch name is a single segment (e.g., `implement-login`), use it as the directory name
- If the branch name has a prefix segment (e.g., `feat/implement-login`), use only the final segment (`implement-login`)
- If the directory already exists, append a numeric suffix (e.g., `implement-login-2`)

Before creating, verify the target directory does not already exist with `ls`.

### Step 3: Create the Worktree

1. Create the worktree with:
```
git worktree add <path> -b <branch-name>
```
Or if the branch already exists:
```
git worktree add <path> <branch-name>
```
`git worktree add` creates intermediate directories automatically.

2. Verify creation:
```
git worktree list
```

### Step 4: Report to User

Tell the user:
- The full path to the new worktree
- The branch name
- How to navigate to it (e.g., `cd <path>`)
- Remind them they can open it in a new editor window

## Guidelines

- Prefer acting autonomously over asking questions. Only ask when genuinely ambiguous.
- Multiple projects may share the same `worktrees/` directory -- this is expected.
- The worktree directory name and branch name may differ (e.g., branch `feat/login` in directory `worktrees/login`).
- Never create a worktree inside the current repository.

Files: 1

Size: 3.5 KB

Complexity: 12/100

Category: General

Source: https://github.com/computomatic/claude-plugin/tree/main/plugins/dev/skills/create-worktree

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts