菜单
Use when working with the repo's moonx root:wt worktree helper, Pierre-managed worktrees, dev-server port offsets, stale server cleanup, Playwright fixtures, or Chrome debug instances. Do not use this as a substitute for host-provided workspace isolation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when running repo scripts, adding or changing dependencies, editing package.json files, installing packages, publishing packages, or deciding when pnpm package operations versus Bun runtime commands should be invoked.
Use when adding or changing packages/apps, TypeScript configs, workspace dependencies, package references, exports, or monorepo project-reference relationships.
Use when adding or running tests, checking snapshots, choosing between Bun tests and Playwright, running lint/format/typecheck, or deciding the verification scope for a change.
Use when preparing, splitting, reviewing, or creating git commits in this repo, especially after larger implementations that should be broken into independently verified commits.
Use when opening, inspecting, clicking, filling, snapshotting, or otherwise automating web pages for this repo, including local dev servers and browser-based verification.
Use when changing loops, collection processing, invalidation logic, tree/diff traversal, path scanning, virtualized rendering calculations, or any code where repeated scans or boolean control flow affect performance or correctness.
| name | worktrees-and-dev-servers |
| description | Use when working with the repo's moonx root:wt worktree helper, Pierre-managed worktrees, dev-server port offsets, stale server cleanup, Playwright fixtures, or Chrome debug instances. Do not use this as a substitute for host-provided workspace isolation. |
Pierre includes a repo-specific git worktree helper for local/manual
parallelization outside host-managed agent workspaces. Managed Pierre worktrees
live at:
~/pierre/pierre-worktrees/<slug>/
Each managed Pierre worktree owns a port offset so dev servers, E2E fixtures, and the Chrome remote-debug instance do not collide. The main clone keeps historical default ports; linked Pierre worktrees shift ports.
If you are already inside a Conductor, Codex, Claude, or other host-provided workspace, do not create another worktree unless the user explicitly asks for a Pierre-managed worktree. Still use this skill when you start repo dev servers or E2E fixtures, because the cleanup and port-offset rules apply to those scripts.
The wt suite is defined in scripts/wt.ts, exposed as the root:wt moon
task, and manages only Pierre-managed worktrees:
moonx root:wt -- new <slug> # create a worktree, allocate offset, pnpm install
moonx root:wt -- rm <slug> # kill its processes, remove the worktree
moonx root:wt -- clean # kill zombie servers on all managed worktree ports
moonx root:wt -- clean <slug> # clean one managed worktree
moonx root:wt -- ps # show per-worktree port status (LISTEN / -)
moonx root:wt -- list # summary of managed + external worktrees
Port-binding moon tasks read the offset from <worktree>/.env.worktree via
their envFile option. Before starting, dev tasks run scripts/run-dev.sh to
kill any stale process bound to the target port.
If you start dev servers, Playwright fixtures, or Chrome debug instances inside a worktree, run cleanup before completing your turn:
moonx root:wt -- clean <slug>
Use moonx root:wt -- clean when you do not know the slug or need to clean
every managed worktree. Use moonx root:wt -- rm <slug> only when intentionally
tearing down the worktree itself.