worktree

Create isolated git worktree workspaces with per-repo configuration and management scripts.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/JoaquinCampo/workspaced-worktrees --skill worktree-joaquincampo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/JoaquinCampo/workspaced-worktrees/tree/main/plugins/worktrees/skills/worktree
Command: npx skills add https://github.com/JoaquinCampo/workspaced-worktrees --skill worktree-joaquincampo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parallel feature development in monorepos often collides with the main checkout; this Skill provides an isolated worktree workspace that lets a Claude Code instance operate on a specific feature branch without disturbing the primary repository, sourcing its configuration from .claude/worktree.json.

Core Features & Use Cases

  • Auto-detects git repos in your project and generates a .claude/worktree.json with per-repo install and start commands.
  • Creates an isolated workspace with per-repo worktrees and generates management scripts (start.sh, stop.sh, cleanup.sh) for unified control.
  • Supports portless and port-based workflows, patching environment variables via repo URL references for seamless cross-service integration.

Quick Start

Run /worktrees:worktree feature/my-feature to create a new isolated worktree workspace for a feature branch.

Frequently Asked Questions about worktree

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

FAQPage Schema
How do I isolate git worktrees for parallel feature development in a monorepo?▼

Isolated git worktrees enable parallel feature work by creating separate workspaces for each branch. This tool auto-discovers git repos, generates a .claude/worktree.json, and derives per-repo service names for seamless branch isolation.

Can I run multiple feature branches simultaneously without disturbing the primary repository checkout?▼

Yes, running multiple feature branches simultaneously without disturbing the primary repository is possible by creating an isolated worktree workspace. It sources configuration from .claude/worktree.json so a Claude Code instance can operate on a specific feature branch independently.

How do I generate management scripts for multiple git worktrees in a monorepo?▼

To generate management scripts for git worktrees, the tool creates an isolated workspace and outputs unified control scripts like start.sh, stop.sh, and cleanup.sh for per-repo worktrees.

Does this worktree tool support patching environment files for cross-service integration?▼

The worktree tool supports patching environment files by using {repo.url} placeholders. It validates per-repo install and start commands, patching environment variables to enable seamless cross-service integration across portless and port-based workflows.

What is the best way to configure per-repo install and start commands for parallel worktree workspaces?▼

Configuring per-repo install and start commands is handled by auto-detecting git repos in your project and generating a .claude/worktree.json file, which validates and configures the commands for each isolated worktree workspace.

When should I not use isolated worktree workspaces for git branch automation?▼

You should not use isolated worktree workspaces if your project lacks multiple git repos or does not require parallel feature development. The tool relies on auto-discovering git repos and generating per-repo configurations to function properly.