ce-worktree
Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch/PR/commit to work on it in isolation. Use when starting isolated work or isolating an existing ref; detects existing isolation first.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/EveryInc/compound-engineering-plugin /tmp/compound-engineering-plugin && ln -s /tmp/compound-engineering-plugin/skills/ce-worktree ~/.claude/skills/ce-worktreeFrom README
Worktree Isolation Ensure the current work happens in an isolated workspace, without disturbing the user's main checkout. Most coding harnesses now create a worktree by default at session start, so the common case is that isolation already exists — detect that first and do not create a redundant one. Order of operations: detect existing isolation -> prefer a native worktree tool -> fall back to plain git. Never create a worktree the harness cannot see. Two modes, set by the caller's need: New work (default). No specific ref named — create a fresh branch from a base (trunk). This is what ce-work uses. Isolate an existing ref. The caller names a ref to work on in isolation — a PR head, an existing branch, or a commit. Attach the worktree to that ref instead of creating a new branch. One hard git rule governs this mode: a branch can be checked out in only one worktree at a time.