sp-git-worktrees

Create, navigate, commit, push, and clean up git worktrees.

Updated Apr 20, 2026

Search Tags:#git #devops #worktrees #branching #repository-management #parallel-development #multitask

Ready to run

npx skills add https://github.com/ddmanyes/antigravity-skills-zht --skill sp-git-worktrees

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sp-git-worktrees
Source: https://github.com/ddmanyes/antigravity-skills-zht/tree/main/skills/sp-git-worktrees
Command: npx skills add https://github.com/ddmanyes/antigravity-skills-zht --skill sp-git-worktrees

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git worktrees let you run multiple independent development contexts from a single repository to keep the main tree clean and avoid constant branch switching.

Core Features & Use Cases

Independent worktrees for each task (feature, bugfix, experiment) to isolate changes.
Quick context switching between worktrees without altering the main branch.
Use Case: develop a new feature in one worktree while bugfixes are tested in another.

Quick Start

Create a new worktree and start working in its directory.

Frequently Asked Questions about sp-git-worktrees

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

FAQPage Schema

What are git worktrees and how do they help with parallel development?▼

Create a git worktree to establish an isolated workspace, navigate to its directory, develop your feature or bugfix, then commit and push directly from that workspace. Clean up the worktree after your task is merged to maintain repository hygiene.

Can I work on a new feature and a hotfix at the same time using git worktrees?▼

Yes, git worktrees support multitasking by providing independent workspaces for each task. You can develop a new feature in one worktree while testing bugfixes in another, enabling rapid context switching without altering the main branch or causing workspace clutter.

Does using git worktrees keep the main repository clean during experiments?▼

Git worktrees keep the main repository clean by isolating experiments, features, and hotfixes in separate directories. This prevents workspace clutter and avoids the need for branch changes in the main tree while running multiple independent development contexts.

What is the best way to clean up a git worktree after merging a branch?▼

The best way to clean up is to follow the workflow of committing and pushing from the worktree workspace, then removing the worktree after the task is merged. This ensures the linked working tree is properly deleted without affecting the main repository.

How do I create a git worktree and start working in its directory?▼

To create a git worktree, use the workflow to establish a new linked working tree for your task, navigate to the new worktree folder, and start developing. This provides an isolated workspace enabling rapid switching for features, experiments, or hotfixes.