How do I install the Worktrees And Dev Servers skill?

Run npx skillmds@latest add pierrecomputer/worktrees-and-dev-servers 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 Worktrees And Dev Servers 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 Worktrees And Dev Servers?

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 Worktrees And Dev Servers free to use?

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

Who published Worktrees And Dev Servers?

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

Worktrees And Dev Servers by pierrecomputer

Name: Worktrees And Dev Servers
Author: pierrecomputer

Worktrees And Dev Servers

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.

File contents

Worktrees and Dev Servers

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.

Worktree Commands

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.

Cleanup Contract

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.

---name: worktrees-and-dev-serversdescription: 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.---# Worktrees and Dev ServersPierre includes a repo-specific `git worktree` helper for local/manualparallelization outside host-managed agent workspaces. Managed Pierre worktreeslive at:```text~/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 keepshistorical default ports; linked Pierre worktrees shift ports.If you are already inside a Conductor, Codex, Claude, or other host-providedworkspace, do not create another worktree unless the user explicitly asks for aPierre-managed worktree. Still use this skill when you start repo dev servers orE2E fixtures, because the cleanup and port-offset rules apply to those scripts.## Worktree CommandsThe `wt` suite is defined in `scripts/wt.ts`, exposed as the `root:wt` moontask, and manages only Pierre-managed worktrees:```bashmoonx root:wt -- new <slug> # create a worktree, allocate offset, pnpm installmoonx root:wt -- rm <slug> # kill its processes, remove the worktreemoonx root:wt -- clean # kill zombie servers on all managed worktree portsmoonx root:wt -- clean <slug> # clean one managed worktreemoonx 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` viatheir `envFile` option. Before starting, dev tasks run `scripts/run-dev.sh` tokill any stale process bound to the target port.## Cleanup ContractIf you start dev servers, Playwright fixtures, or Chrome debug instances insidea worktree, run cleanup before completing your turn:```bashmoonx root:wt -- clean <slug>```Use `moonx root:wt -- clean` when you do not know the slug or need to cleanevery managed worktree. Use `moonx root:wt -- rm <slug>` only when intentionallytearing down the worktree itself.

Frequently asked questions