Claude Code CommandGit Workflow11 installs

Worktree Init

Create parallel worktrees for multi-task development with Ghostty panels

Install with the Claude Code Templates CLI
$ npx claude-code-templates@latest --command="git-workflow/worktree-init" --yes

Requires Claude Code. The command adds this command to your project's .claudedirectory — nothing runs on ToolZip's servers.

What's inside this command

Component source

Worktree Parallel Init

Create multiple git worktrees for parallel development: $ARGUMENTS

Instructions

You are setting up parallel worktrees so the user can work on multiple tasks simultaneously in separate Ghostty terminal panels, each running its own Claude instance.

Step 1: Validate Environment

  • Check this is a git repository: git rev-parse --is-inside-work-tree
  • Get the repo name: basename $(git rev-parse --show-toplevel)
  • Get the main branch name (check for main or master): git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' — if that fails, default to main
  • Ensure working tree is clean: git status --porcelain. If dirty, warn the user and ask if they want to continue.
  • Fetch latest: git fetch origin

Step 2: Parse Tasks

Parse tasks from $ARGUMENTS. Tasks are separated by | (pipe character).

If $ARGUMENTS is empty, use AskUserQuestion to ask the user to describe their tasks (they can provide multiple separated by |).

For each task description:

  • Trim whitespace
  • Generate a kebab-case branch name: claude/<kebab-case-task> (max 50 chars, alphanumeric and hyphens only)
  • Generate a worktree directory path: ../worktrees/<repo-name>/claude-<kebab-case-task>

Step 3: Create Worktrees

For each task:

  • Create the parent directory if needed: mkdir -p ../worktrees/<repo-name>
  • Create the worktree:
git worktree add -b claude/<name> ../worktrees/<repo-name>/claude-<name> origin/<main-branch>

  • Write a .worktree-task.md file inside the new worktree with this content:
# Worktree Task

   **Branch:** claude/<name>
   **Task:** <original task description>
   **Created:** <ISO date>
   **Source repo:** <path to main repo>

Step 4: Check for Dependencies

If a package.json exists in the repo root, note that each worktree may need npm install (or the appropriate package manager).

Check for:

  • package-lock.json → npm install
  • yarn.lock → yarn install
  • pnpm-lock.yaml → pnpm install
  • bun.lockb → bun install

Step 5: Output Summary

Display a clear summary table:

| # | Task | Branch | Path |
|---|------|--------|------|
| 1 | ... | claude/... | ../worktrees/repo/claude-... |

Then display ready-to-copy commands for Ghostty panels. For each worktree:

# Panel <N>: <task description>
cd <absolute-path-to-worktree> && claude

If dependencies were detected, add a note:

# Note: Run <package-manager> install in each worktree before starting

Finally, remind the user:

  • Open a new Ghostty panel with Cmd+D (split right) or Cmd+Shift+D (split down)
  • When done with a task, use /worktree-deliver to commit, push, and create a PR
  • After merging all PRs, use /worktree-cleanup --all from the main repo
Type
Command
Category
Git Workflow
Installs
11
Source
GitHub ↗

Related Claude Code Commands

Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.