# Worktrees

> Guide for using git worktrees to parallelize development with coding agents. Use this skill when the user requests to work in a new worktree or wants to work on a separate feature in isolation (e.g., "Work in a new worktree", "Create a worktree for feature X").

- **Type:** Skill
- **Install:** `agentstack add skill-maragudk-skills-worktrees`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [maragudk](https://agentstack.voostack.com/s/maragudk)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [maragudk](https://github.com/maragudk)
- **Source:** https://github.com/maragudk/skills/tree/main/worktrees

## Install

```sh
agentstack add skill-maragudk-skills-worktrees
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Git Worktrees for Parallel Development

## Overview

This skill enables parallel development by using git worktrees. Each worktree provides an isolated working directory with its own branch, allowing multiple agents to work on different features simultaneously without conflicts.

## When to Use This Skill

Use this skill when:
- User explicitly requests to work in a new worktree (e.g., "Work in a new worktree")
- User wants to develop a feature in isolation while preserving the main working directory
- Multiple agents need to work on different tasks in parallel

## Workflow

### 1. Determine Branch Name

Choose a descriptive branch name for the feature or task to be worked on. The branch name should follow standard git naming conventions (lowercase, hyphen-separated, e.g., `add-user-authentication`, `fix-login-bug`).

### 2. Create Worktree

Create a new worktree in the `.worktrees/` directory within the current project:

```bash
git worktree add .worktrees/ -b 
```

This command:
- Creates a new directory at `.worktrees/`
- Creates and checks out a new branch named ``
- Links the worktree to the current repository

### 3. Switch to Worktree

Change the working directory to the newly created worktree:

```bash
cd .worktrees/
```

### 4. Work in Isolation

Proceed with development tasks in the worktree. This environment is completely isolated from the main working directory, allowing independent work without interference.

All standard git operations (commit, push, pull, etc.) work normally within the worktree.

**Note:** If this project runs services (web apps, docker-compose, etc.), see [apps.md](apps.md) for setup steps including environment file copying, port allocation, and service startup.

### 5. List Active Worktrees (Optional)

To view all active worktrees:

```bash
git worktree list
```

This displays all worktrees, their paths, and the branches they're on.

### 6. Remove Worktree (Optional)

When you're done with a worktree, you can remove it:

```bash
git worktree remove .worktrees/
```

**Note:** Don't automatically remove worktrees. Leave that decision to the user. If the worktree is running services (see [apps.md](apps.md)), make sure to stop those services first before removing the worktree.

## Important Notes

- The `.worktrees/` directory should be added to `.gitignore` if not already present
- Each worktree maintains its own working directory but shares the same git repository
- Worktrees enable true parallel development without the need for stashing or branch switching
- After creating and switching to a worktree, inform the user of the new working directory path

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [maragudk](https://github.com/maragudk)
- **Source:** [maragudk/skills](https://github.com/maragudk/skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-maragudk-skills-worktrees
- Seller: https://agentstack.voostack.com/s/maragudk
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.