Using Git Worktrees

Git worktrees create isolated working directories linked to the same repository, allowing concurrent feature work without cross-branch interference. This skill automates worktree creation, enforcing safety checks and baseline setups to ensure a clean starting point.

Managing project-local Git worktrees safely involves using a designated directory like .worktrees and ensuring it is properly gitignored. This skill automates that detection and creation workflow, preventing accidental commits of worktree folders into the main repository.

To set up a Git worktree using repository conventions, the skill detects project-local directories, reads CLAUDE.md preferences, or uses user prompts. It then creates the isolated worktree and runs project setup and baseline tests automatically.

Yes, Git worktrees can be hosted in global locations like ~/.config. This skill supports flexible placement by following prioritized detection rules, allowing you to host concurrent feature work outside the main project folder.

Running baseline tests during Git worktree setup ensures the isolated environment has a clean, functional starting point. This skill automatically executes project setup and tests after creating the worktree to verify the new workspace is ready for feature development.

Yes, Git worktree creation honors CLAUDE.md guidance when present. The skill implements a prioritized workflow that checks project-local directories first, then falls back to CLAUDE.md preferences or direct user prompts to determine the worktree location.