create-worktree

Create git worktrees for parallel feature development with shared CODEX sessions.

26|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/sburl/CrossCheck --skill create-worktree-sburl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-worktree
Source: https://github.com/sburl/CrossCheck/tree/main/codex/skills/create-worktree
Command: npx skills add https://github.com/sburl/CrossCheck --skill create-worktree-sburl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git worktrees let you have multiple working directories from the same repository, enabling parallel feature development without constant branch switching or context loss.

Core Features & Use Cases

  • Create new worktrees tied to specific branches for isolated development sessions and Codex coordination.
  • Share a single PR counter across all worktrees to streamline reviews.
  • Copy project scaffolding (CODEX, .codex) into each new worktree to maintain consistency.
  • Support guidance for parallel development workflows across teams.

Quick Start

Run /create-worktree <branch-name> [base-branch] to spin up a new worktree and auto-load CODEX.md.

Frequently Asked Questions about create-worktree

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

FAQPage Schema
How do I set up multiple Git worktrees for parallel feature development?

Create multiple Git worktrees by running a command like /create-worktree <branch-name> [base-branch] to spin up isolated working directories tied to specific branches for simultaneous feature development.

What are Git worktrees and when do I need them for branch management?

Git worktrees are multiple working directories linked to a single repository, needed when you want to run parallel branches for features or bug fixes without constant context switching or branch cloning.

Does the parallel worktree workflow support sharing a single PR counter across branches?

Yes, the parallel worktree workflow supports sharing a single PR counter across all worktrees, streamlining code reviews while maintaining isolated development sessions for each branch.

How do I copy CODEX configurations into a new Git worktree?

Copying CODEX configurations into a new Git worktree happens automatically during creation, cloning project scaffolding like .codex files to maintain consistent Codex sessions across all parallel directories.

Can I use Git worktrees to avoid context switching during bug fixes and experiments?

Yes, you can use Git worktrees to avoid context switching during bug fixes and experiments by maintaining separate working directories for each task, preserving your primary branch state.

Are there limitations when coordinating cross-worktree sessions for shared git hooks?

Cross-worktree session coordination relies on a unified directory structure and deterministic creation, meaning limitations arise if your repository structure deviates from standard git hooks integration patterns.