ce-worktree

Creates and manages isolated Git worktrees for separate branches.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/lucking7/compound-engineering-skills --skill ce-worktree-lucking7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-worktree
Source: https://github.com/lucking7/compound-engineering-skills/tree/main/skills/ce-worktree
Command: npx skills add https://github.com/lucking7/compound-engineering-skills --skill ce-worktree-lucking7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that work happens in an isolated git worktree, keeping the main checkout clean and undisturbed.

Core Features & Use Cases

  • Isolation Detection: Detects if the current directory is already a linked worktree.
  • Native Worktree Tool Usage: Preferably uses the harness's native worktree tool.
  • Git Fallback: Fallbacks to plain git if no native tool is available.
  • Worktree Operations: Provides operations for listing, removing, and switching to a worktree.
  • Use Case: When reviewing a PR, you can use this skill to ensure that your work is isolated from the main checkout.

Quick Start

Run the ce-worktree skill to create a new worktree for your work.

Frequently Asked Questions about ce-worktree

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

FAQPage Schema
How do I isolate my git branch work to keep the main checkout clean?

To isolate branch work and keep the main checkout clean, you can use a git worktree. This approach creates a separate working directory linked to your repository, allowing you to switch branches without affecting the main checkout state.

What is the best way to review a PR without disturbing my current git checkout?

The best way to review a PR without disturbing your current checkout is by using an isolated git worktree. This allows you to fetch and review the PR changes in a separate directory while your main checkout remains completely undisturbed.

How do I create and manage separate git worktrees for different branches?

You can create and manage separate git worktrees by using native worktree tools or falling back to plain git commands. This setup supports operations like listing, removing, and switching between isolated worktrees for different branches.

Does this worktree isolation method work without native harness tools?

Yes, worktree isolation works without native harness tools by falling back to plain git commands. If the directory is already a linked worktree, it is automatically detected, ensuring the isolation mechanism functions regardless of the environment.

When do I need to use an isolated git worktree instead of a standard branch switch?

You need an isolated git worktree when you want to work on separate branches simultaneously without affecting the main checkout. This is particularly useful for code review or context switching, ensuring your main checkout stays clean and stable.