Our review
Creates Git worktrees in a standardized location with proper DVC configuration and .env file copying.
Strengths
- Automates worktree creation with a consistent directory structure.
- Copies the .env file to preserve environment variables.
- Configures DVC cache sharing to save disk space.
Limitations
- Assumes the project uses .env and DVC.
- Does not handle worktree removal or listing.
- Worktree names must match branch names.
When you need to work on multiple branches simultaneously without switching directories.
When you don't need isolated working directories or the project does not use Git or DVC.
Security analysis
SafeThe skill uses only safe shell commands (mkdir, git, cp, cat) to create git worktrees and copy configuration files. It does not exfiltrate data, execute destructive operations, or disable safety measures. No external tools are required beyond standard git and shell utilities.
No concerns found
Examples
Create a git worktree for a new branch called feature/add-loginSet up a worktree for an existing branch named fix/issue-42I need to work on multiple branches simultaneously. Please create a worktree for bugfix/error-handlingname: worktree description: This skill should be used when the user asks to "create a worktree", "add a worktree", "set up a worktree", mentions "git worktree", or wants to work on multiple branches simultaneously. user-invocable: true
Create Git Worktree
This skill creates git worktrees in a standardized location with proper DVC configuration.
When to Use
Use this skill when the user:
- Asks to create a new git worktree
- Wants to work on multiple branches simultaneously
- Mentions "git worktree add" or similar
Worktree Location
All worktrees are created under .worktrees/ in the repository root:
repo/
├── .worktrees/
│ ├── feature-branch-1/
│ └── feature-branch-2/
├── src/
└── ...
Instructions
1. Determine the Repository Root
Find the git repository root:
git rev-parse --show-toplevel
2. Create the Worktrees Directory
Ensure the .worktrees directory exists:
mkdir -p "$(git rev-parse --show-toplevel)/.worktrees"
3. Create the Worktree
Create the worktree with the specified branch:
REPO_ROOT="$(git rev-parse --show-toplevel)"
git worktree add "$REPO_ROOT/.worktrees/<branch-name>" <branch-name>
If creating a new branch:
git worktree add -b <new-branch-name> "$REPO_ROOT/.worktrees/<new-branch-name>"
4. Copy .env File
Copy .env from the project root to the worktree so environment variables are available:
REPO_ROOT="$(git rev-parse --show-toplevel)"
WORKTREE_PATH="$REPO_ROOT/.worktrees/<branch-name>"
# Copy .env if it exists
[ -f "$REPO_ROOT/.env" ] && cp "$REPO_ROOT/.env" "$WORKTREE_PATH/"
5. Handle DVC Configuration (if applicable)
Check if the repository uses DVC by looking for .dvc/ directory:
if [ -d "$(git rev-parse --show-toplevel)/.dvc" ]; then
echo "DVC detected"
fi
If DVC is present and .dvc/config.local exists, copy and update it:
- Copy the local config:
REPO_ROOT="$(git rev-parse --show-toplevel)"
WORKTREE_PATH="$REPO_ROOT/.worktrees/<branch-name>"
cp "$REPO_ROOT/.dvc/config.local" "$WORKTREE_PATH/.dvc/config.local"
- Update the cache directory to point to the main repo's cache:
REPO_ROOT="$(git rev-parse --show-toplevel)"
WORKTREE_PATH="$REPO_ROOT/.worktrees/<branch-name>"
cat > "$WORKTREE_PATH/.dvc/config.local" << EOF
[cache]
dir = $REPO_ROOT/.dvc/cache
EOF
Note: If the original .dvc/config.local contains other settings beyond cache configuration, preserve those settings and only update/add the cache dir setting.
Complete Example
Creating a worktree for branch feature/new-api:
REPO_ROOT="$(git rev-parse --show-toplevel)"
BRANCH_NAME="feature/new-api"
WORKTREE_DIR="$REPO_ROOT/.worktrees/$BRANCH_NAME"
mkdir -p "$REPO_ROOT/.worktrees"
git worktree add "$WORKTREE_DIR" "$BRANCH_NAME"
# Copy .env if it exists
[ -f "$REPO_ROOT/.env" ] && cp "$REPO_ROOT/.env" "$WORKTREE_DIR/"
if [ -f "$REPO_ROOT/.dvc/config.local" ]; then
mkdir -p "$WORKTREE_DIR/.dvc"
cat > "$WORKTREE_DIR/.dvc/config.local" << EOF
[cache]
dir = $REPO_ROOT/.dvc/cache
EOF
fi
echo "Worktree created at: $WORKTREE_DIR"
Notes
- Worktree names typically match branch names, with slashes replaced by the filesystem
- The
.worktrees/directory should be added to.gitignoreif not already - Use
git worktree listto see all worktrees - Use
git worktree remove <path>to remove a worktree
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.