Git Workflow Manager FAQs

Question 1

Do I need to stash my changes before switching features?

Accepted Answer

No. Because each feature or fix exists in its own isolated worktree directory, you can simply move between folders without stashing or committing unfinished work.

Question 2

Where are the worktrees stored?

Accepted Answer

By default, worktrees are created in a sibling directory to your main repository (e.g., project-name-worktrees/) to keep your main development folder clean and focused.

Question 3

Is this skill compatible with my specific project type?

Accepted Answer

Yes, the Git Workflow Manager is 100% generic and works with any project that uses Git for version control, regardless of the programming language or framework.

Question 4

How does the cleanup process work?

Accepted Answer

The skill includes a cleanup command that identifies worktrees whose branches have already been merged into the main branch, allowing you to safely delete the directories and prune the git worktree list.

Question 5

What is a git worktree and how does this skill use them?

Accepted Answer

A git worktree allows you to have multiple branches of the same repository checked out simultaneously in different directories. This skill automates their creation using GitFlow naming conventions to keep your work organized.

Git Workflow Manager

Key Features

Use Cases

Git Workflow Manager

Key Features

Use Cases