team-worktree

Create isolated git worktrees for task-specific development branches.

8|1|Updated Mar 28, 2026

Search Tags:#automation #git #workflow #development #isolation #worktree

Ready to run

npx skills add https://github.com/bostonaholic/team --skill team-worktree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-worktree
Source: https://github.com/bostonaholic/team/tree/main/skills/team-worktree
Command: npx skills add https://github.com/bostonaholic/team --skill team-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of context switching and branch pollution by creating isolated git worktrees for specific development tasks, ensuring that implementation work remains separate from the main repository checkout.

Core Features & Use Cases

Isolated Workspaces: Automatically creates a git worktree per repository involved in a task, preventing interference between concurrent development pipelines.
Multi-Repo Support: Handles complex features spanning multiple repositories by synchronizing worktree creation across the entire project set.
Safety Guardrails: Prevents nesting worktrees and ensures implementation never occurs directly on the default branch.

Quick Start

Ask the team to set up a worktree for the current task by typing team-worktree in your terminal.

Frequently Asked Questions about team-worktree

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

FAQPage Schema

How do I isolate development branches to prevent context switching in git?▼

Git worktrees allow you to isolate development branches by creating dedicated working directories for each task, preventing branch pollution. This skill automates worktree creation to keep implementation work separate from the main repository checkout and avoid context switching.

How do I set up isolated git worktrees for a multi-repository project?▼

To set up isolated git worktrees across multiple repositories, this skill synchronizes worktree creation for each repository involved in a task. It maps task-specific directories to dedicated git worktrees, ensuring concurrent development pipelines do not interfere with each other.

Can I use git worktrees to work directly on the default branch?▼

No, you cannot use this approach to work directly on the default branch. The skill enforces safety guardrails that prevent nesting worktrees and ensures implementation never occurs directly on the default branch, protecting your main repository state.

What do I need to automate git worktree creation for isolated development?▼

To automate git worktree creation, you need git and standard shell utilities installed in your environment. The skill uses these dependencies to verify repository state and execute worktree operations safely without requiring additional external components.

Why use automated git worktrees instead of standard git branching?▼

Automated git worktrees provide isolated workspaces for each task, unlike standard branching which keeps files in a single directory. This prevents context switching and branch pollution by mapping task-specific directories to dedicated worktrees across single or multiple repositories.