git-worktree

Create, list, switch, and clean up Git worktrees with .env copying.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/isndotbiz/website --skill git-worktree-isndotbiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-worktree
Source: https://github.com/isndotbiz/website/tree/main/.claude/skills/git-worktree
Command: npx skills add https://github.com/isndotbiz/website --skill git-worktree-isndotbiz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill simplifies the management of Git worktrees, providing an isolated and streamlined way to handle parallel development, code reviews, and feature work without the complexities of manual Git commands.

Core Features & Use Cases

  • Create Worktrees: Easily create new worktrees from a specified branch (defaults to main), ensuring .env files are copied and .gitignore is updated.
  • List & Switch: View all active worktrees and seamlessly switch between them.
  • Cleanup: Safely remove completed worktrees with interactive confirmation.
  • Use Case: When reviewing a pull request, if you're not on the target branch, this skill can create an isolated worktree for the PR, allowing you to review code without disrupting your current work, and then clean it up afterward.

Quick Start

Use the git-worktree skill to create a new worktree for the feature-login branch.

Frequently Asked Questions about git-worktree

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use git worktrees for parallel development without losing my current changes?

Git worktrees provide isolated directories for parallel development, allowing you to switch feature branches without stashing current changes. This skill creates worktrees automatically while copying .env files and updating .gitignore for seamless workflows.

What is the best way to review a pull request without disrupting my current git workflow?

Creating an isolated git worktree is the best way to review pull requests without disruption. This skill sets up a dedicated worktree for the PR branch, letting you review code independently before safely cleaning it up.

How do I manage .env files and .gitignore when creating multiple git worktrees?

When creating git worktrees, managing .env files manually is tedious. This skill automates .env file copying and .gitignore updates during worktree creation, ensuring isolated parallel development environments stay configured correctly.

Can I list and switch between active git worktrees during feature development?

Yes, you can view all active git worktrees and seamlessly switch between them. This skill handles listing and switching worktrees, streamlining parallel feature development and code review workflows without complex git commands.

How do I safely remove completed git worktrees after finishing a code review?

To safely remove completed git worktrees, use cleanup features with interactive confirmation. This skill ensures finished worktrees are deleted securely after code reviews, preventing leftover directories from cluttering your workspace.

Does git worktree workflow require manual branch management for isolated feature work?

No, git worktree workflows do not require manual branch management for isolated work. This skill handles creation from specified branches like main, automating setup so you can focus on parallel development and reviews.