ce-worktree

Create isolated git worktrees for parallel feature development and PR reviews.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/KingInYellows/yellow-plugins --skill ce-worktree-kinginyellows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-worktree
Source: https://github.com/KingInYellows/yellow-plugins/tree/main/RESEARCH/upstream-snapshots/e5b397c9d1883354f03e338dd00f98be3da39f9f/plugins/compound-engineering/skills/ce-worktree
Command: npx skills add https://github.com/KingInYellows/yellow-plugins --skill ce-worktree-kinginyellows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Create isolated worktrees to work on parallel features or PR reviews without disturbing the main checkout.

Core Features & Use Cases

  • Copies .env*, .env.local, .env.test, etc. from the main repository into the new worktree (skips .env.example)
  • Trusts mise/direnv configs with branch-aware safety rules so review branches do not auto-trust untrusted .envrc content
  • Adds .worktrees to .gitignore in the main repository if not already ignored
  • Fetches the base from the selected branch and creates the worktree without modifying the main checkout

Quick Start

Create a new worktree by running the worktree-manager script with the desired branch name.

Frequently Asked Questions about ce-worktree

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

FAQPage Schema
How do I isolate feature development without disturbing my main git checkout?

To isolate feature development without disturbing your main git checkout, create a dedicated git worktree. This fetches the selected base branch and sets up a parallel working directory, leaving the main repository untouched.

Does creating a git worktree copy my environment files automatically?

Yes, creating a git worktree copies .env*, .env.local, and .env.test files from the main repository into the new worktree automatically. It skips .env.example files during the environment file copy process.

How does git worktree handle direnv and mise configs for safe PR reviews?

Git worktree applies branch-aware safety rules to direnv and mise configurations. This ensures that review branches do not auto-trust untrusted .envrc content, providing safe testing across multiple branches.

Do I need to manually update .gitignore when using parallel git worktrees?

No, you do not need to manually update .gitignore. The worktree creation process automatically adds .worktrees to .gitignore in the main repository if it is not already ignored.

What is the best way to work on parallel git branches for multiple features?

The best way to work on parallel git branches is using git worktrees for environment isolation. This allows safe testing across multiple branches and parallel work without modifying the main checkout.

Can I review PRs in an isolated environment without affecting my current branch?

Yes, you can review PRs in an isolated environment by creating a dedicated git worktree. It fetches the PR branch and applies branch-aware trust rules for dev tools, isolating the review process from your main checkout.