ck:worktree

You create isolated git worktrees by running a command that auto-detects monorepo structures, sanitizes branch names, and sets up a separate directory. This enables parallel feature development without modifying your main repository.

The best way to manage git worktrees in a monorepo is using smart root detection that identifies the topmost superproject and submodules. This ensures worktrees are created at the correct root path for organized branch management.

Yes, you can preview worktree creation by using the dry-run feature. This shows the target path and sanitized branch name without actually modifying your repository, ensuring safe branch management before execution.

Yes, git worktree creation preserves uncommitted work and supports environment template copying. It automatically copies .env*.example files to your new worktree, with traversal safety checks to prevent incorrect file overwrites.

To handle complex branch names with slashes, use the optional --no-prefix mode. This preserves slashes and case for Jira or multi-segment branches, overriding the default slug sanitization during worktree creation.

When removing a git worktree with a dirty state, the script provides clear warnings about uncommitted changes. Path validation and robust error reporting ensure you do not accidentally lose uncommitted work during worktree removal.