flow-next-worktree-kit

Git worktrees allow you to maintain isolated workspaces for parallel feature development. This Skill automates worktree creation and applies safety checks to keep branches separate without polluting your main workspace.

To copy .env files into new git worktrees, the workspace management script automatically propagates non-sensitive environment configurations during worktree creation to preserve config context across isolated branches.

You need git worktrees when you require isolated workspaces for parallel feature development on different branches. This approach shares a single repository history, avoiding the disk overhead of multiple full clones.

Yes, this workspace management workflow requires git as its sole dependency. The orchestration logic runs entirely through a single bash script, ensuring compatibility wherever git is installed.

When creating git worktrees, the script enforces safety checks and path validations, along with optional origin and base branch handling, to ensure safe creation and prevent accidental workspace overwrites or conflicts.

The best way to clean up git worktrees after a feature review is to use the script's cleanup command, which safely removes isolated workspaces and ensures your main working directory remains tidy and unpolluted.