Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Based on SOC occupation classification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/caidanw/skills --skill git-worktreeThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | git-worktree |
| description | Create, remove, and list git worktrees in a standardized location |
| alwaysAllow | ["Bash"] |
Manage git worktrees stored in ~/.git-worktrees/<repo>/<branch>, keeping them out of the user's project directories.
Before any operation, determine the repository name:
repo=$(basename "$(git rev-parse --show-toplevel)")
The worktree base directory is always ~/.git-worktrees/$repo/.
If the user provides just a branch name, treat it as a create operation.
repo=$(basename "$(git rev-parse --show-toplevel)")
branch="<branch>"
dir="$HOME/.git-worktrees/$repo/$branch"
mkdir -p "$HOME/.git-worktrees/$repo"
git worktree add "$dir" "$branch"
If the branch doesn't exist yet, use -b to create it from HEAD:
git worktree add -b "$branch" "$dir" HEAD
After creation, always prominently display the worktree path so the user can open a new session pointing to it:
Worktree created at:
~/.git-worktrees/<repo>/<branch>
repo=$(basename "$(git rev-parse --show-toplevel)")
git worktree remove "$HOME/.git-worktrees/$repo/<branch>"
If the worktree has uncommitted changes, warn the user before using --force.
git worktree list
Clean up stale worktree references (e.g., after manually deleting a worktree directory):
git worktree prune
--force without explicit user confirmationWrite clean, terse technical docs — commits, issues, PRDs, specs, and technical communication
Write clean, pragmatically functional TypeScript — simple, composable, soundly typed
Use clear, natural, reader-centered language for all agent communication. Apply when the user asks for plain language, clear communication, writing inspired by Simplified Technical English or ISO 24495-1, or Orwell-style clarity. Enable a persistent mode only when the user invokes /clear-communication or explicitly asks to keep this style active.