How do I install the Agent Worktrees skill?

Run npx skillmds@latest add tjcages/agent-worktrees in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Worktrees safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Worktrees?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Worktrees free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agent Worktrees?

tjcages (@tjcages) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Worktrees by tjcages — Agent Skill

Name: Agent Worktrees
Author: tjcages

Agent Worktrees

Isolate parallel AI agents on one git repo via branch+worktree, shared env symlinks, auto-ported previews, status lines, claims, and a land-from-main ritual. Use when ≥2 agents will touch this or any repo, the user asks to set up worktrees / parallel agents / agent isolation, or an agent is about to share a working tree with another. NOT for ordinary single-agent work on main.

tjcages 948012d 4 files · 2.1 KB Updated Sep 17, 2026

File contents

Agent worktrees

Chat: RESPONSE.md. Full method: METHODOLOGY.md.

Operating order

1. Should we isolate? (§1)

≥2 agents on this repo → yes. User/product says share → obey. Overlapping structural files → serialize even with worktrees.

2. Already isolated?

If you're already in a worktree (common dir ≠ toplevel of a single checkout) and a branch exists for this task → skip create; run setup if share links missing.

3. Create branch + worktree (§2.1)

Off main. Prefer Linear branch name when tracked. Don't double-create Claude Code's claude/<name> trees.

4. Share env (§2.2)

bash scripts/worktree.sh setup

Symlink, never copy. Configure share list for this stack (see METHODOLOGY §2.2 table).

5. Preview + claim + status (§2.3–2.5)

Own auto-ported server. Declare <branch> · <task>. End every message with:

🔌 <branch> · <one-line task> · <preview URL>

6. Land + teardown (§2.6–2.7)

bash scripts/worktree.sh land <branch>
git push origin main
bash scripts/worktree.sh teardown ../<repo>-<slug> <branch>

Clear the claim. Stop the preview before teardown.

7. Done check (§6)

Rubric ≥10/12, no zeros.

Install into a repo

See METHODOLOGY §4. Prefer existing repo scripts/worktree.sh; else copy from this pack. Optional worktree.share. Write the six-step protocol into agent instructions; smoke-test once.

Out of scope

Single-agent main-tree work. Schema-migration strategy beyond "serialize on shared DB." Idle-time autopull (sibling concern).

---name: agent-worktreesdescription: Isolate parallel AI agents on one git repo via branch+worktree, shared env symlinks, auto-ported previews, status lines, claims, and a land-from-main ritual. Use when ≥2 agents will touch this or any repo, the user asks to set up worktrees / parallel agents / agent isolation, or an agent is about to share a working tree with another. NOT for ordinary single-agent work on main.---# Agent worktreesChat: [RESPONSE.md](./RESPONSE.md). Full method: [METHODOLOGY.md](./METHODOLOGY.md).## Operating order### 1. Should we isolate? (§1)≥2 agents on this repo → yes. User/product says share → obey. Overlapping structural files → serialize even with worktrees.### 2. Already isolated?If you're already in a worktree (common dir ≠ toplevel of a single checkout) and a branch exists for this task → skip create; run `setup` if share links missing.### 3. Create branch + worktree (§2.1)Off `main`. Prefer Linear branch name when tracked. Don't double-create Claude Code's `claude/<name>` trees.### 4. Share env (§2.2)```bashbash scripts/worktree.sh setup```Symlink, never copy. Configure share list for this stack (see METHODOLOGY §2.2 table).### 5. Preview + claim + status (§2.3–2.5)Own auto-ported server. Declare `<branch> · <task>`. End every message with:`🔌 <branch> · <one-line task> · <preview URL>`### 6. Land + teardown (§2.6–2.7)```bashbash scripts/worktree.sh land <branch>git push origin mainbash scripts/worktree.sh teardown ../<repo>-<slug> <branch>```Clear the claim. Stop the preview before teardown.### 7. Done check (§6)Rubric ≥10/12, no zeros.## Install into a repoSee METHODOLOGY §4. Prefer existing repo `scripts/worktree.sh`; else copy from this pack. Optional `worktree.share`. Write the six-step protocol into agent instructions; smoke-test once.## Out of scopeSingle-agent main-tree work. Schema-migration strategy beyond "serialize on shared DB." Idle-time autopull (sibling concern).

Frequently asked questions