worktrees:new

To create a Git worktree for parallel development, you use a command specifying a name and optionally a base branch. This isolates your feature work into a separate directory without polluting your main workspace checkout.

Nested worktree checkouts appear if the directory is not ignored. This skill automatically validates and ensures the .worktrees path is properly added to your gitignore configuration to prevent repository pollution.

Yes, you can create a worktree from a specific base branch by using the --base argument. This allows you to start your parallel development from any existing branch rather than the default repository branch.

You can lock a newly created Git worktree by passing the --lock argument during creation. This prevents the worktree from being accidentally pruned or modified while you are actively working in it.

Using isolated Git worktrees is the best way to manage parallel development branches. This approach creates separate directory workspaces for each branch, keeping your main checkout clean and preventing file conflicts.