worktree

Create isolated git worktrees per task with branch naming and environment separation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ebijun1007/vibe-coding --skill worktree-ebijun1007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.claude/skills/worktree
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill worktree-ebijun1007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This rule enables parallel development by using git worktree for each new task or issue, ensuring isolated workspaces and clean branch naming.

Core Features & Use Cases

  • Create a dedicated worktree per task, with branch naming like issue-NN and isolated environment.
  • Enforce one worktree per task, separable DB/PORT per worktree, and environment handling (.envrc and 1Password).
  • Manage transitions between tasks with checks to avoid mixing changes in a single worktree.

Quick Start

When starting a new task, create a new worktree for the issue and switch into it to begin work.

Frequently Asked Questions about worktree

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

FAQPage Schema
How do I manage parallel development tasks in the same Git repository without mixing changes?

Parallel development is managed by using a dedicated git worktree per task, isolating workstreams with clean branch naming conventions like issue-NN to prevent mixing changes in a single workspace.

What is the best way to isolate database and port configurations when working on multiple branches simultaneously?

The best way to isolate environments is by applying per-workspace environment separation within each git worktree, using .envrc files and 1Password alongside separable DB and PORT configurations.

How do I start a new issue-driven workflow using git worktree?

To start an issue-driven workflow, create a new git worktree for the specific issue, switch into the isolated workspace, and begin development with enforced branch naming conventions and environment isolation.

Can I enforce one worktree per task to prevent branch switching conflicts?

Yes, you can enforce one worktree per task with built-in guardrails around task switching, ensuring environment separation and preventing the mixing of changes across multiple tasks.

Does git worktree work with direnv and 1Password for environment isolation?

Yes, git worktree supports environment isolation by managing per-workspace configurations through .envrc files for direnv and 1Password, ensuring separable DB and PORT settings across worktrees.