using-git-worktrees

Git worktrees isolate feature work by creating a separate working directory linked to your repository. This skill automates worktree creation on a new branch, keeping your main workspace clean and stable for parallel development or experiments.

Using git worktrees is the best way to manage parallel branches, allowing you to check out multiple branches simultaneously in different directories. This skill automates directory discovery and setup to streamline switching between features without cloning.

To ensure git worktrees are safely ignored, this skill verifies your .gitignore rules and automatically updates them with a commit if the worktree directory is not already excluded. This prevents worktree files from polluting your main repository status.

Yes, this git worktree workflow handles project setup by detecting the project context and running the appropriate setup commands for your package managers. This ensures your new worktree has dependencies installed and a validated clean baseline before you start coding.

Yes, you can use git worktrees for hotfix isolation to instantly create a clean workspace from your main branch without affecting ongoing feature work. This skill automates the branch creation and directory selection so you can immediately patch critical issues.

You need a git worktree when starting feature work or experiments that require an isolated directory, avoiding the instability of switching branches in your main workspace. It is ideal for keeping your main repository clean while testing changes in parallel.