worktree

Git worktrees isolate parallel agent changes by creating separate working directories for each task within a single repository. This prevents cross-task interference and branch contention while enabling faster iteration without polluting the main branch.

Create a new worktree for your task to start making isolated changes there. The skill supports per-task worktree creation with standardized naming conventions, ensuring easy maintenance and automated cleanup of stale worktrees when tasks are complete.

The best way to manage multiple parallel branches is using git worktrees to isolate each task or experiment. This approach enforces standardized naming conventions and supports automated cleanup of stale worktrees, reducing merge conflicts and maintenance overhead.

Yes, git worktrees enable parallel experimentation within a single repository lifecycle by isolating each task in its own working directory. This prevents branch contention and allows multiple experiments to run safely without polluting the main branch.

Stale worktrees from completed tasks are handled through automated cleanup supported by the skill. Standardized naming conventions make it easy to identify and remove worktrees that are no longer needed, keeping the repository maintained.

Git worktrees may not be necessary for simple, sequential single-branch workflows where parallel task isolation is not required. They are best suited for scenarios involving multiple concurrent tasks or experiments that need isolated branches and safe merges.