gwt

Centralize Git worktrees into a single directory with consistent naming.

Updated Oct 27, 2025

Search Tags:#worktrees #workflow-automation #command-line #branch-management #git-worktree #parallel-development #repository-organization

Ready to run

npx skills add https://github.com/SomtoUgeh/dotfiles --skill gwt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gwt
Source: https://github.com/SomtoUgeh/dotfiles/tree/main/claude/skills/gwt
Command: npx skills add https://github.com/SomtoUgeh/dotfiles --skill gwt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nested worktrees and scattered development directories clutter projects, hinder reviews, and slow down parallel work.

Core Features & Use Cases

Centralized worktrees folder: keeps all worktrees under one directory (e.g., ~/code/worktrees) to maintain a clean main repo.
Consistent naming: uses {repo-name}--{branch-name} to prevent collisions and simplify discovery.
Rich command surface: provides gwt new, gwt ls, gwt go, gwt switch, gwt rm, gwt here, and gwt path for fast, predictable workflows.
Collaboration-friendly: allows PRs from worktrees while sharing the same git database and remotes.
Safe environment handling: copies environment-related files on creation for consistent local setups.

Quick Start

Create a new worktree: gwt new feat/my-feature
Switch to an existing worktree: gwt switch feat/my-feature
List available worktrees: gwt ls

Frequently Asked Questions about gwt

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

FAQPage Schema

How do I organize Git worktrees into a single directory to prevent nested folders?▼

You can organize git worktrees into a single directory by centralizing them under a dedicated path like ~/code/worktrees. This prevents nested worktrees and keeps your main repository clean by enforcing explicit worktree creation and path-based navigation.

What is the best way to manage parallel development branches without scattering directories?▼

Centralized git worktrees provide the best way to manage parallel development branches without scattering directories. They use a consistent {repo-name}--{branch-name} naming scheme to prevent collisions and simplify branch discovery across isolated reviews.

How do I switch between existing Git worktrees from the command line?▼

You can switch between existing git worktrees using a dedicated switch command with the target branch name. This navigates directly to the correct centralized worktree path without manually searching your file system.

Do I need external tooling to use centralized Git worktrees for branch management?▼

No external tooling is needed to use centralized git worktrees for branch management. This workflow relies entirely on standard Git worktree features, requiring no additional dependencies to create, list, switch, and remove worktrees.

Can I submit pull requests from a Git worktree while sharing the same repository database?▼

Yes, you can submit pull requests from a git worktree while sharing the same repository database and remotes. This collaboration-friendly setup allows isolated reviews and parallel development without duplicating your local git configuration.

Why does creating a Git worktree copy environment-related files?▼

Creating a git worktree copies environment-related files to ensure consistent local setups across parallel development branches. This safe environment handling guarantees that each isolated worktree maintains the necessary local configuration for building and testing.