make-worktree

To create a git worktree with standardized branch naming, this Skill automatically generates branches based on specified types like feature, fix, chore, refactor, docs, test, and perf, while resolving the correct directory path for the new worktree environment.

When creating a git worktree, this Skill handles submodule initialization by automatically running updates for all Git submodules, ensuring the new worktree environment has the correct nested repository states without manual intervention.

No, creating a git worktree with this Skill does not require manually trusting the mise configuration, as it automatically handles mise trust for new worktree environments to ensure your development tools are ready immediately.

The best way to manage multiple git development branches without switching directories is using git worktrees, which allow you to check out multiple branches simultaneously in separate paths, keeping your development workflow organized and isolated.

Yes, you can resolve the directory path automatically when setting up a git worktree, as this Skill features intelligent path resolution that determines the correct directory for the worktree and falls back to sensible defaults or prompts if needed.

You should use a git worktree instead of a standard branch for feature development because it allows you to maintain a dedicated directory for each branch, eliminating the need to stash changes and enabling immediate focus on coding with proper submodule initialization.