How do I install the Tree Me skill?

Run npx skillmds@latest add webcoyote/tree-me 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 Tree Me 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 Tree Me?

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

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

Who published Tree Me?

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

Tree Me by webcoyote — Agent Skill

Name: Tree Me
Author: webcoyote

Tree Me

Use this skill when to create a git worktree, checkout a branch in isolation, work on a PR in a separate workspace, manage git worktrees, or when the user mentions "tree-me". Provides guidance on using the tree-me CLI tool for isolated git worktree workspaces.

webcoyote c05ba09 2.1 KB Updated Sep 17, 2026

File contents

tree-me — Git Worktree Management

tree-me manages git worktrees organized at $WORKTREE_ROOT/<repo>/<branch> (default: ~/dev/worktrees).

Commands

Command	Description
`tree-me create <branch> [base]`	Create new branch in a worktree (base defaults to main/master)
`tree-me checkout <branch>`	Checkout existing branch in a new worktree
`tree-me pr <number\|url>`	Checkout a GitHub PR in a worktree (uses `gh`)
`tree-me list`	List all worktrees
`tree-me remove <branch>`	Remove a worktree
`tree-me prune`	Remove stale worktree admin files

Key Behaviors

Idempotent: If a worktree for the branch already exists, prints its path instead of erroring.
Auto-cd: If the user has source <(tree-me shellenv) in their shell config, the shell auto-cds into the new worktree after create/checkout/pr.
PR branches: tree-me pr 123 creates a local branch named pr-123 and checks it out.
co and rm and ls are aliases for checkout, remove, and list.

Worktree Path Convention

~/dev/worktrees/<repo-name>/<branch-name>/

Override root with WORKTREE_ROOT env var.

Common Workflows

Start isolated work on a new feature:

tree-me create my-feature        # branches from main
tree-me create my-feature develop # branches from develop

Review a PR without disturbing current work:

tree-me pr 456

Clean up after merging:

tree-me remove my-feature

When Helping the User

Prefer tree-me create for new work, tree-me checkout for existing branches.
After creating a worktree, remind the user to cd into it (or that auto-cd handles it if shellenv is sourced).
Use tree-me list to check existing worktrees before creating a duplicate.
tree-me prune is safe to run when worktrees have been deleted manually.

---name: tree-medescription: Use this skill when to create a git worktree, checkout a branch in isolation, work on a PR in a separate workspace, manage git worktrees, or when the user mentions "tree-me". Provides guidance on using the tree-me CLI tool for isolated git worktree workspaces.---# tree-me — Git Worktree Management`tree-me` manages git worktrees organized at `$WORKTREE_ROOT/<repo>/<branch>` (default: `~/dev/worktrees`).## Commands| Command | Description ||---|---|| `tree-me create <branch> [base]` | Create new branch in a worktree (base defaults to main/master) || `tree-me checkout <branch>` | Checkout existing branch in a new worktree || `tree-me pr <number\|url>` | Checkout a GitHub PR in a worktree (uses `gh`) || `tree-me list` | List all worktrees || `tree-me remove <branch>` | Remove a worktree || `tree-me prune` | Remove stale worktree admin files |## Key Behaviors- **Idempotent**: If a worktree for the branch already exists, prints its path instead of erroring.- **Auto-cd**: If the user has `source <(tree-me shellenv)` in their shell config, the shell auto-`cd`s into the new worktree after `create`/`checkout`/`pr`.- **PR branches**: `tree-me pr 123` creates a local branch named `pr-123` and checks it out.- **`co` and `rm` and `ls`** are aliases for `checkout`, `remove`, and `list`.## Worktree Path Convention```~/dev/worktrees/<repo-name>/<branch-name>/```Override root with `WORKTREE_ROOT` env var.## Common Workflows**Start isolated work on a new feature:**```bashtree-me create my-feature # branches from maintree-me create my-feature develop # branches from develop```**Review a PR without disturbing current work:**```bashtree-me pr 456```**Clean up after merging:**```bashtree-me remove my-feature```## When Helping the User- Prefer `tree-me create` for new work, `tree-me checkout` for existing branches.- After creating a worktree, remind the user to `cd` into it (or that auto-cd handles it if shellenv is sourced).- Use `tree-me list` to check existing worktrees before creating a duplicate.- `tree-me prune` is safe to run when worktrees have been deleted manually.

Frequently asked questions