git-worktree-manager

To run parallel Git worktrees safely, you need deterministic port allocation and .env synchronization to isolate each runtime environment. This Skill coordinates safe worktree creation, copying environment files and assigning non-conflicting ports to prevent collisions during parallel feature development.

The best way to clean up dirty Git worktrees safely is to detect stale, dirty, and merged branches before removal. This Skill performs dirty-tree checks and merged-branch detection to reduce the chance of accidental data loss during stale worktree maintenance.

Yes, you can use Git worktrees for multi-agent sessions and hotfix isolation. This Skill supports parallel feature development by preparing isolated runtime environments, allowing a team to keep separate worktrees for main integration, features, and hotfixes simultaneously.

To sync .env files and install dependencies in a new Git worktree, request worktree creation with optional dependency installation. This Skill copies environment files, allocates predictable ports, and prepares each worktree to run like its own local application.

Yes, Git worktree management supports JSON or text CLI automation. This Skill provides text and JSON output formats, enabling automated scripts to handle worktree creation, environment synchronization, and cleanup workflows programmatically.