worktree-kit

Managing git worktrees for parallel feature development involves using a script to create isolated worktrees under a dedicated .worktrees directory, allowing you to separate features cleanly without manual setup. This enables isolated reviews and clean workspaces.

To copy .env files to a new git worktree, you can use a dedicated copy-env command that duplicates non-overwriting environment files into the target worktree. This preserves per-feature configurations without overwriting existing environment variables.

The best way to clean up unused git worktrees without deleting branches is to use a cleanup command that safely removes worktree directories while preserving the associated feature branches. This ensures your main branches remain untouched during workspace maintenance.

Yes, you can switch between git worktrees for isolated code reviews by using a list and switch command. This allows you to quickly navigate between feature branches in separate directories without stashing changes or cloning the repository again.

No, git worktree management with this approach does not require manual directory setup. The script automatically enforces safety rules and stores all worktrees under a dedicated .worktrees directory, simplifying the creation process.