ce-worktree

Automates isolated git worktree creation for parallel feature development and PR reviews.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill ce-worktree-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-worktree
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/compound-engineering/skills/ce-worktree
Command: npx skills add https://github.com/xotong/claude-marketplace --skill ce-worktree-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, mise, direnv, and includes scripts (resource) components.

What problem does it solve?

Create isolated git worktrees to work on features in parallel without touching the main checkout, enabling safer PR reviews and experiments.

Core Features & Use Cases

  • Create a dedicated worktree at .worktrees/<branch> that branches from a specified base, fetches origin when available, and does not modify the main checkout.
  • Copy environment files from the main repository into the new worktree (skipping .env.example) to preserve local config.
  • Automatically trust or prompt for dev-tools configs (mise and direnv) based on the base branch to balance convenience and safety.
  • Use cases include parallel feature development, PR review workflows, and experimentation that must remain isolated from the main branch.

Quick Start

Create a new worktree for a feature branch using the bundled script.

Frequently Asked Questions about ce-worktree

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create isolated git worktrees for parallel feature work without disturbing the main checkout?

To create isolated git worktrees, this Skill automates branching from a specified base and fetches origin into a dedicated .worktrees/<branch> directory, leaving your main checkout completely untouched. It enables safer parallel feature development and PR reviews.

How do I copy environment files into a new git worktree automatically?

Copying environment files into a new git worktree happens automatically during creation, transferring your local config from the main repository while skipping .env.example. This preserves your environment setup for parallel work across branches.

Do I need mise and direnv to automate git worktree creation?

You do not strictly need mise and direnv to create git worktrees, but they are optional dev-tools dependencies. The Skill automatically trusts or prompts for their configurations based on the base branch to balance convenience and safety.

What is the best way to manage parallel environment configurations across git branches?

Managing parallel environment configurations across git branches is best handled by creating isolated worktrees that copy local environment files from the main repository. This ensures each parallel feature branch retains necessary config without manual duplication.

Can I use git worktrees for PR review workflows without affecting my current branch?

You can use git worktrees for PR review workflows without affecting your current branch. The Skill creates an isolated checkout at .worktrees/<branch> for experiments and reviews, ensuring the main working directory remains stable and unmodified.