git-worktree

Git worktrees enable parallel feature development by creating isolated working directories linked to the same repository, allowing you to manage multiple branches simultaneously without context switching. This Skill automates worktree creation, status tracking, and cleanup.

Agent isolation in git branch management assigns each AI agent a dedicated worktree, ensuring focused and independent task execution without interference. This Skill creates separate worktree environments so concurrent development sessions do not conflict.

Yes, you can manage concurrent development sessions without merge conflicts by creating isolated git worktrees for each task. This Skill supports creating and tracking separate worktree environments, preventing interference between parallel branches.

Yes, you need Git command-line tools installed to manage isolated worktree environments. This Skill requires Git command-line tools for repository operations and uses JSON for metadata management to track worktree status and progress.

The best way to track progress across multiple git worktrees is using a metadata management system that records status and updates. This Skill provides status tracking and progress updating for isolated worktree environments using JSON metadata.

You should avoid git worktrees for branch management when working on a single linear task with no need for parallel development or agent isolation. Worktrees add directory and metadata overhead that is unnecessary for sequential feature development.