git-worktree

Create and remove Git worktrees with safety checks and validation.

16|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/sbluemin/fleet-harness --skill git-worktree-sbluemin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-worktree
Source: https://github.com/sbluemin/fleet-harness/tree/main/.agents/skills/git-worktree
Command: npx skills add https://github.com/sbluemin/fleet-harness --skill git-worktree-sbluemin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation and management of Git worktrees, ensuring a consistent and efficient workflow.

Core Features & Use Cases

  • Single Procedure Integration: Unifies the creation and removal of Git worktrees into one procedure.
  • Mode-Based Workflow: Supports creation and removal of worktrees, with detailed input handling for each mode.
  • User-Friendly: Allows users to easily add or remove worktrees with minimal technical knowledge.
  • Use Case: For a developer who wants to experiment with new features without affecting their main codebase, this skill can be used to create a new worktree quickly.

Quick Start

To create a new Git worktree, run the following command: use git-worktree create <worktree-name>.

Frequently Asked Questions about git-worktree

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

FAQPage Schema
How do I create a Git worktree from a specific branch?

To create a Git worktree, you can use a mode-based workflow that requests the worktree name and validates the branch before safely generating the new working directory for isolated feature development.

What is the best way to manage the lifecycle of Git worktrees?

Managing Git worktree lifecycles involves unifying creation and removal procedures into a single workflow with defined safety checks, ensuring valid directories are added or cleanly removed without affecting the main codebase.

Can I safely remove an active Git worktree without losing changes?

Yes, you can safely remove the current active Git worktree by triggering the removal mode, which performs validation checks before executing operational instructions to ensure no unintended local changes are lost.

When do I need to use a Git worktree in my development workflow?

You need a Git worktree when you want to experiment with new features or run parallel branches simultaneously without affecting or switching away from your main codebase in the current directory.

Does Git worktree creation require advanced version control knowledge?

Git worktree creation requires minimal technical knowledge because the workflow handles mode routing and provides clear, step-by-step execution instructions for users to easily add or remove worktrees.