flow-next-worktree-kit

You can manage git worktrees for parallel development by creating, listing, and switching isolated worktrees stored under a .worktrees directory, keeping your main workspace completely undisturbed during feature work.

Safe git worktree cleanup uses built-in safety checks that prevent dangerous operations on symlink paths and block deletions on non-clean worktrees, ensuring you avoid unintended data loss during workspace removal.

Yes, you can copy environment files into new git worktrees. The copy-env functionality preserves per-workspace configurations during feature development, ensuring isolated branches have the necessary local environment setup automatically.

Git worktree management supports CI pipelines and multiple repository recovery workflows by enabling isolated review and parallel experimental branches across projects, ensuring safe workspace cleanups in automated environments.

Using a dedicated script for git worktree creation ensures worktrees are safely stored under .worktrees with safety checks against symlinks, while automatically copying environment files to preserve per-workspace configurations natively.

When using git worktrees, limitations include safety checks that prevent dangerous operations on symlink paths and block cleanup on non-clean worktrees, protecting against unintended deletions but requiring manual resolution.