菜单
Manage git worktrees with their own dev ports, symlinked .env files, playground, and simulations. Use when the user asks to create, set up, list, enter, or remove a worktree.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/rhesis-ai/rhesis --skill worktree命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Colour, font and design-token rules for the docs site — when hex is banned, when it is correct, and which surfaces ignore the theme. Use when styling docs components or editing CSS under docs/src.
How the docs site generates per-page og:image cards, and the cache and font traps when changing them. Use when editing the OG card design, og-theme.js, or a page's social preview image.
Add a new Enterprise Edition feature behind a feature gate, across backend and frontend. Use when adding an EE-only capability such as SSO.
| name | worktree |
| description | Manage git worktrees with their own dev ports, symlinked .env files, playground, and simulations. Use when the user asks to create, set up, list, enter, or remove a worktree. |
Run ./rh worktree $ARGUMENTS from the repo root. Why worktrees must go through this command at
all — and how the WorktreeCreate hook routes EnterWorktree into it — is in AGENTS.md; this
skill is the command surface.
If the user gave no arguments, ask which operation they want:
| Command | What it does |
|---|---|
./rh worktree <name> | Create a worktree branching from current HEAD, with its own dev ports |
./rh worktree --init | Give an existing worktree the same setup — run it from inside that worktree |
./rh worktree <name> --load | Launch a shell in the worktree |
./rh worktree <name> --remove | Remove the worktree, its dev containers and volumes, and its branch |
./rh worktree --list | List all worktrees |
./rh worktree help prints the same list with per-flag detail.
--init on an existing worktreeFor a worktree made with a bare git worktree add, or one the hook only partly set up. Run it
from inside the worktree — it locates the main checkout itself:
cd ~/worktrees/rhesis/<name> && ./rh worktree --init
From the main checkout, name the target instead: ./rh worktree <name> --init.
It allocates a free port block into .rhesis-ports, symlinks playground/, simulations/,
domain.local/, the .env files and the Claude config, then copies apps/backend/.env and
apps/frontend/.env.local and shifts their ports. It's idempotent — re-running reports what's
already linked and leaves it alone.
Two things it won't do: run in the main checkout, or touch a directory git doesn't list as a worktree. Both exit with an error rather than provisioning the wrong tree.
If the worktree's branch predates the --init flag, its own ./rh won't have it. Run the main
checkout's copy instead — it resolves the target from your current directory, not from where the
script lives:
/path/to/main/rh worktree --init
~/worktrees/rhesis/ gets provisioned fine, but --load and --remove
can't find it by name — remove it with git worktree remove after ./rh dev clean inside it.--remove deletes the branch too, and only deletes it if it's fully merged../rh dev status inside it shows the ports it actually got.