flow-next-worktree-kit

Create, list, switch, and cleanup git worktrees with .env file copying.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/tiendung/flow-next --skill flow-next-worktree-kit-tiendung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-worktree-kit
Source: https://github.com/tiendung/flow-next/tree/main/skills/flow-next-worktree-kit
Command: npx skills add https://github.com/tiendung/flow-next --skill flow-next-worktree-kit-tiendung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill helps developers manage parallel feature work by creating isolated git worktrees and copying environment files, preventing workspace contamination and simplifying review workflows.

Core Features & Use Cases

  • Create, list, switch, and cleanup Git worktrees under the .worktrees directory for isolated feature development
  • Copy local .env files into new worktrees to preserve environment parity across tasks
  • Use cases include parallel feature branches, isolated code reviews, and quick cleanups of stale workspaces

Quick Start

Run the worktree.sh script to create a new worktree for your feature.

Frequently Asked Questions about flow-next-worktree-kit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage git worktrees for parallel feature branches without contaminating my workspace?

Git worktree management isolates parallel feature branches by creating separate working directories under a designated .worktrees directory, preventing workspace contamination and simplifying isolated code reviews.

How do I copy .env files into new git worktrees to preserve environment parity?

Copying .env files into new git worktrees preserves environment parity across tasks by duplicating local environment configurations into newly created isolated workspaces during the setup process.

Can I use this worktree script to switch between feature branches and clean up stale workspaces?

The worktree script supports switching between isolated feature branches and cleaning up stale workspaces through deterministic operations, ensuring safe removal of unused working directories.

Does git worktree management work safely with symlinks and environment isolation?

Git worktree management enforces safety checks for symlinks and constrains all worktrees to a specific .worktrees directory, ensuring reliable environment isolation for parallel development.

What is the best way to isolate code reviews using git worktrees?

Isolating code reviews using git worktrees creates dedicated working directories for each branch, allowing reviewers to test features independently without affecting the main repository environment.

Why should I constrain git worktrees to a single .worktrees directory?

Constraining git worktrees to a single .worktrees directory ensures deterministic operations and simplifies cleanup of stale workspaces while maintaining strict environment isolation across parallel tasks.