ce-worktree

Creates isolated git worktrees with environment files and dev-tool trust configuration.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-worktree-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-worktree
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-worktree
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-worktree-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Setting up a git worktree for parallel feature work or PR review normally requires manual steps: copying .env files, trusting mise/direnv configs, and updating .gitignore. This Skill automates that setup so a new worktree is ready to use immediately without disturbing the main checkout. ## Core Features & Use Cases - Automated Worktree Creation: Creates a worktree under .worktrees/<branch> from a specified base branch, fetching the base ref without modifying the main checkout. - Environment File Copying: Copies .env, .env.local, .env.test and similar files from the main repo while skipping .env.example and backing up existing files. - Branch-Aware Dev Tool Trust: Auto-trusts mise and direnv configs only when they match a trusted baseline branch, skipping direnv allow on untrusted review branches for safety. - Use Case: While reviewing a teammate's PR, create an isolated worktree with bash scripts/worktree-manager.sh create feat/login so your main checkout stays free for your own in-progress work. ## Quick Start Ask the assistant to create a worktree for your branch by running the worktree-manager script with a meaningful branch name like feat/login.

Frequently Asked Questions about ce-worktree

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

FAQPage Schema
How do I create a git worktree for parallel feature work?

Run bash scripts/worktree-manager.sh create <branch-name> from the main repo. It creates .worktrees/<branch-name> from the default branch, copies .env files, and configures dev tool trust so the worktree is ready to use.

How do I review a PR without switching branches in my main checkout?

Create a worktree for the PR branch using the worktree-manager script, then cd into .worktrees/<branch> to review it. Your main checkout stays untouched, and you can remove the worktree afterward with git worktree remove.

Does the worktree script copy .env files automatically?

Yes, it copies all .env* files from the main repo except .env.example, backing up any pre-existing destination files. For worktrees created without them, run cp .env* .worktrees/<branch>/ from the main repo.

Why was direnv trust skipped when creating my worktree?

direnv allow is only auto-run for trusted base branches like main, develop, or release/* whose configs match the baseline. For feature or review branches, review the config diff and run the printed direnv allow command manually.

When should I not use a git worktree?

Skip worktrees for single-task work that can happen on a branch in the main checkout. Worktrees are meant for parallel feature work, PR reviews, or keeping the default branch free of in-progress state.