git-worktree

Manage parallel git worktrees with slot-based ports and lifecycle operations.

1|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/przbadu/skills-factory --skill git-worktree-przbadu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-worktree
Source: https://github.com/przbadu/skills-factory/tree/main/skills/git-worktree
Command: npx skills add https://github.com/przbadu/skills-factory --skill git-worktree-przbadu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the friction of juggling multiple feature branches by setting up isolated git worktrees with predictable ports and startup commands for parallel development.

Core Features & Use Cases

  • Create and Remove Worktrees: Spin up or tear down paired Rails and frontend worktrees for a branch without manually wiring the environment each time.
  • Slot-Based Port Management: Assign deterministic Rails, Vite, and ActionCable ports so multiple worktrees can run side by side without collisions.
  • Lifecycle Operations: List active slots, inspect worktree details, start servers, stop processes, and clean up merged worktrees safely.
  • Use Case: A developer can work on several GitHub issues at once, keep each branch isolated, and quickly bring up the right backend and frontend servers for each task.

Quick Start

Ask the git-worktree skill to create a new worktree for your branch, assign an available slot, and start the backend and frontend servers.

Frequently Asked Questions about git-worktree

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

FAQPage Schema
How do I run multiple git branches in parallel without port conflicts?

Git worktree parallel development assigns deterministic Rails, Vite, and ActionCable ports using slot-based management, so multiple branches run side by side without collisions. Each worktree gets isolated ports and startup commands automatically.

What is the best way to manage git worktrees for backend and frontend feature work?

Git worktree management creates and removes paired Rails and frontend worktrees for a branch without manually wiring the environment each time. It handles listing, starting, stopping, and cleaning up worktrees through lifecycle operations.

Do I need jq to manage git worktrees with slot-based port assignment?

Yes, jq is required for git worktree slot-based port management because it handles the registry operations that track assigned ports and active worktrees. You also need git worktree support and shell tooling for process control and environment file generation.

How do I clean up merged git worktrees and free up development slots?

Git worktree cleanup safely removes merged worktrees and frees their assigned slots. The lifecycle operations handle tearing down paired Rails and frontend worktrees, stopping processes, and releasing the deterministic ports assigned to that branch.

Can I use git worktrees for parallel development with Vite and Rails?

Yes, git worktree parallel development supports paired Rails and frontend worktrees with Vite. It assigns deterministic ports for Rails, Vite, and ActionCable so multiple worktrees run simultaneously without port collisions across active slots.

Why does running multiple Rails servers in separate worktrees cause port conflicts?

Multiple Rails servers in separate worktrees cause port conflicts because they default to the same ports. Git worktree slot-based port management solves this by assigning deterministic, non-overlapping ports to each worktree for Rails, Vite, and ActionCable.