How do I install the Worktree skill?

Run npx skillmds@latest add domengabrovsek/worktree 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 Worktree 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 Worktree?

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 Worktree free to use?

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

Who published Worktree?

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

Worktree by domengabrovsek — Agent Skill

Name: Worktree
Author: domengabrovsek

Worktree

Creates an isolated git worktree for the current task and switches into it, resolving cross-session collisions before they happen. Use when the user says '/worktree <slug>' or wants an isolated working copy for a new task.

File contents

Create a worktree for: $ARGUMENTS

Slug

If $ARGUMENTS is non-empty, treat the first argument as the slug.

If $ARGUMENTS is empty:

If a plan file exists at .claude/state/plans/<latest>.md in the current project, derive slug from its basename (strip date prefix and .md extension).
Else generate <topic>-<6char-hex> and ask the user to confirm.

The slug must be lowercase, hyphen-separated, no spaces.

Branch type

Default to feat/<slug>. If the user's request looks like a bug fix, use fix/<slug>. For cleanups, chore/<slug>.

Steps

Find the repo root: git rev-parse --show-toplevel. Refuse if not inside a git repo.
Compute target dir: <repo-parent>/<repo-basename>-<slug>. Refuse if it already exists (offer to cd into the existing one instead).

Create the worktree on a new branch:

git worktree add "<target>" -b "<branch>"

cd into the worktree dir for all subsequent operations.
Show the user the new working dir, branch name, and confirm next steps.

After creation

The worktree is its own working tree - the PreToolUse guard auto-bypasses inside it. The session can continue mutating files freely without colliding with the main checkout's session.

When work is done:

Open a PR from the worktree's branch as normal.
After merge, run /worktree-merge to clean up the worktree and remove the local branch.

Frequently asked questions