Do I need to stash my changes before switching branches with GWT?

No, because each branch operates in its own dedicated worktree directory, your uncommitted changes remain safe in their specific path without requiring stashing.

Does GWT support remote branch tracking?

Yes, GWT features smart remote lookup that can automatically find and track branches from your configured Git remotes when you attempt to switch to them.

How does GWT differ from standard Git worktree commands?

GWT provides a higher-level abstraction that automates directory path management, provides centralized storage, and offers a more intuitive CLI for switching and cleaning up branches.

Where are GWT worktrees stored on my machine?

GWT stores worktrees in a centralized directory located at ~/.gwt_store, which keeps your main project folder clean and organized.

Can I use GWT to clean up after a Pull Request is merged?

Yes, GWT includes specific commands to remove the worktree and delete the local branch simultaneously, making post-merge cleanup fast and efficient.

GWT Git Worktree Manager

Name: GWT Git Worktree Manager
Author: troydai

bytroydai

•

Developer Tools

Streamlines Git branch management by leveraging isolated worktrees for seamless context switching without stashing.

GWT is a specialized Git worktree management skill designed to optimize development workflows by allowing you to work on multiple branches simultaneously in separate directories. By replacing traditional branch checkouts with automated worktree creation, GWT eliminates the need for stashing changes and prevents the 'dirty working directory' problem. It features centralized storage in a hidden store to keep your local repositories clean, smart remote branch tracking, and simplified cleanup commands for post-merge maintenance. This skill is ideal for developers managing complex parallel features or frequent context switching for code reviews.