Git Worktree 管理器 - 高效并行开发与代码审查工具，支持自动环境配置

git-worktree by everyinc/compound-engineering-plugin

280 周安装量

10,900 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/everyinc/compound-engineering-plugin --skill git-worktree

开发自动化命令行工具

🇨🇳中文介绍

Git Worktree 管理器

此技能为您的开发工作流提供了统一的 Git 工作树管理界面。无论您是进行独立的 PR 审查还是并行处理功能，此技能都能处理所有复杂性。

此技能的功能

创建工作树：从主分支创建，并使用清晰的命名
列出工作树：显示当前状态
在工作树之间切换：实现并行工作
自动清理已完成的工作树
每个步骤的交互式确认
工作树目录的自动 .gitignore 管理
从主仓库自动复制 .env 文件到新工作树
自动信任开发工具配置：针对 mise 和 direnv 配置，并带有审查安全防护措施

重要提示：始终使用管理器脚本

切勿直接调用 git worktree add。 请始终使用 worktree-manager.sh 脚本。

该脚本处理原始 git 命令无法处理的关键设置：

从主仓库复制 .env、.env.local、.env.test 等文件

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

何时使用此技能

在以下场景中使用此技能：

代码审查 (/ce:review)：如果当前不在目标分支（PR 分支或请求的分支）上，则提供用于独立审查的工作树
功能开发 (/ce:work)：始终询问用户是希望使用并行工作树还是直接在分支上工作
并行开发：当同时处理多个功能时
清理：在工作树中完成工作后

在 Claude Code 工作流中

此技能会自动从 /ce:review 和 /ce:work 命令调用：

# 用于审查：如果不在 PR 分支上，则提供工作树
# 用于开发：始终询问 - 新分支还是工作树？

您也可以直接从 bash 调用此技能：

# 创建新工作树（自动复制 .env 文件）
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-login

# 列出所有工作树
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh list

# 切换到某个工作树
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh switch feature-login

# 将 .env 文件复制到现有工作树（如果之前未复制）
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh copy-env feature-login

# 清理已完成的工作树
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

`create <branch-name> [from-branch]`

使用给定的分支名称创建一个新的工作树。

branch-name（必需）：新分支和工作树的名称
from-branch（可选）：创建分支的基准分支（默认为 main）

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-login

检查工作树是否已存在
从远程更新基准分支
创建新的工作树和分支
从主仓库复制所有 .env 文件（.env, .env.local, .env.test 等）
基于分支感知的安全规则信任开发工具配置：
- 受信任的基础分支（main、develop、dev、trunk、staging、release/*）与自身进行比较
- 其他分支与默认分支进行比较
- 在非受信任的基础分支上跳过 direnv 自动允许，因为 .envrc 可能引用未经检查的文件
显示用于切换到工作树的路径

列出所有可用的工作树及其分支和当前状态。

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh list

工作树名称
分支名称
当前所在的工作树（用 ✓ 标记）
主仓库状态

`switch <name>` 或 `go <name>`

切换到现有的工作树并进入其目录。

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh switch feature-login

如果未提供名称，则列出可用的工作树并提示选择

`cleanup` 或 `clean`

交互式清理非活动工作树，并请求确认。

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

列出所有非活动工作树
请求确认
移除选定的工作树
清理空目录

使用工作树进行代码审查

# Claude Code 识别到您不在 PR 分支上
# 提供选项："使用工作树进行独立审查？(y/n)"

# 您回答：yes
# 脚本运行（自动复制 .env 文件）：
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create pr-123-feature-name

# 您现在位于用于审查的独立工作树中，并拥有所有环境变量
cd .worktrees/pr-123-feature-name

# 审查完成后，返回主目录：
cd ../..
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

# 对于第一个功能（复制 .env 文件）：
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-login

# 稍后，开始第二个功能（也复制 .env 文件）：
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-notifications

# 列出您拥有的工作树：
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh list

# 根据需要切换：
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh switch feature-login

# 完成后返回主目录并清理：
cd .
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

KISS（保持简单）

一个管理器脚本处理所有工作树操作
简单的命令和合理的默认值
交互式提示防止误操作
清晰的命名直接使用分支名称

工作树始终从 main 分支创建（除非指定）
工作树存储在 .worktrees/ 目录中
分支名称即为工作树名称
.gitignore 自动管理

创建前确认工作树
清理前确认以防止意外删除
不会删除当前工作树
清晰错误信息处理问题

与工作流的集成

并非总是创建工作树：

1. 检查当前分支
2. 如果**已经**在目标分支（PR 分支或请求的分支）上 → 保持原状，无需工作树
3. 如果**不同**于审查目标分支 → 提供工作树：
   "使用工作树进行独立审查？(y/n)"
   - 是 → 调用 git-worktree 技能
   - 否 → 在当前分支上继续 PR 差异比较

始终提供选择：

1. 询问："您希望如何工作？
   1. 在当前工作树上创建新分支（实时工作）
   2. 工作树（并行工作）"

2. 如果选择 1 → 正常创建新分支
3. 如果选择 2 → 调用 git-worktree 技能从 main 分支创建

"工作树已存在"

如果看到此消息，脚本将询问您是否要切换到该工作树。

"无法移除工作树：它是当前工作树"

首先切换出该工作树（返回主仓库），然后清理：

cd $(git rev-parse --show-toplevel)
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

在工作树中迷失了方向？

查看当前位置：

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh list

工作树中缺少 .env 文件？

如果工作树创建时没有 .env 文件（例如，通过原始的 git worktree add），请复制它们：

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh copy-env feature-name

导航回主目录：

cd $(git rev-parse --show-toplevel)

.worktrees/
├── feature-login/          # 工作树 1
│   ├── .git
│   ├── app/
│   └── ...
├── feature-notifications/  # 工作树 2
│   ├── .git
│   ├── app/
│   └── ...
└── ...

.gitignore (已更新以包含 .worktrees)

使用 git worktree add 创建独立环境
每个工作树都有自己的分支
一个工作树中的更改不会影响其他工作树
与主仓库共享 git 历史记录
可以从任何工作树推送

工作树是轻量级的（仅为文件系统链接）
无需复制仓库
共享 git 对象以提高效率
比克隆或暂存/切换快得多

🇺🇸English

Git Worktree Manager

This skill provides a unified interface for managing Git worktrees across your development workflow. Whether you're reviewing PRs in isolation or working on features in parallel, this skill handles all the complexity.

What This Skill Does

Create worktrees from main branch with clear branch names
List worktrees with current status
Switch between worktrees for parallel work
Clean up completed worktrees automatically
Interactive confirmations at each step
Automatic .gitignore management for worktree directory
Automatic .env file copying from main repo to new worktrees
Automatic dev tool trusting for mise and direnv configs with review-safe guardrails

CRITICAL: Always Use the Manager Script

NEVER callgit worktree add directly. Always use the worktree-manager.sh script.

The script handles critical setup that raw git commands don't:

Copies .env, .env.local, .env.test, etc. from main repo
Trusts dev tool configs with branch-aware safety rules:
- mise: auto-trust only when unchanged from a trusted baseline branch
- direnv: auto-allow only for trusted base branches; review worktrees stay manual
Ensures .worktrees is in .gitignore
Creates consistent directory structure

# ✅ CORRECT - Always use the script

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-name

# ❌ WRONG - Never do this directly
git worktree add .worktrees/feature-name -b feature-name main

When to Use This Skill

Use this skill in these scenarios:

Code Review (/ce:review): If NOT already on the target branch (PR branch or requested branch), offer worktree for isolated review
Feature Work (/ce:work): Always ask if user wants parallel worktree or live branch work
Parallel Development : When working on multiple features simultaneously
Cleanup : After completing work in a worktree

How to Use

In Claude Code Workflows

The skill is automatically called from /ce:review and /ce:work commands:

# For review: offers worktree if not on PR branch
# For work: always asks - new branch or worktree?

Manual Usage

You can also invoke the skill directly from bash:

# Create a new worktree (copies .env files automatically)
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-login

# List all worktrees
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh list

# Switch to a worktree
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh switch feature-login

# Copy .env files to an existing worktree (if they weren't copied)
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh copy-env feature-login

# Clean up completed worktrees
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

Commands

`create <branch-name> [from-branch]`

Creates a new worktree with the given branch name.

Options:

branch-name (required): The name for the new branch and worktree
from-branch (optional): Base branch to create from (defaults to main)

Example:

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-login

What happens:

Checks if worktree already exists
Updates the base branch from remote
Creates new worktree and branch
Copies all .env files from main repo (.env, .env.local, .env.test, etc.)
Trusts dev tool configs with branch-aware safety rules:
- trusted bases (main, develop, dev, trunk, staging, release/*) compare against themselves
- other branches compare against the default branch
- direnv auto-allow is skipped on non-trusted bases because .envrc can source unchecked files
Shows path for cd-ing to the worktree

`list` or `ls`

Lists all available worktrees with their branches and current status.

Example:

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh list

Output shows:

Worktree name
Branch name
Which is current (marked with ✓)
Main repo status

`switch <name>` or `go <name>`

Switches to an existing worktree and cd's into it.

Example:

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh switch feature-login

Optional:

If name not provided, lists available worktrees and prompts for selection

`cleanup` or `clean`

Interactively cleans up inactive worktrees with confirmation.

Example:

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

What happens:

Lists all inactive worktrees
Asks for confirmation
Removes selected worktrees
Cleans up empty directories

Workflow Examples

Code Review with Worktree

# Claude Code recognizes you're not on the PR branch
# Offers: "Use worktree for isolated review? (y/n)"

# You respond: yes
# Script runs (copies .env files automatically):
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create pr-123-feature-name

# You're now in isolated worktree for review with all env vars
cd .worktrees/pr-123-feature-name

# After review, return to main:
cd ../..
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

Parallel Feature Development

# For first feature (copies .env files):
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-login

# Later, start second feature (also copies .env files):
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh create feature-notifications

# List what you have:
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh list

# Switch between them as needed:
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh switch feature-login

# Return to main and cleanup when done:
cd .
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

Key Design Principles

KISS (Keep It Simple, Stupid)

One manager script handles all worktree operations
Simple commands with sensible defaults
Interactive prompts prevent accidental operations
Clear naming using branch names directly

Opinionated Defaults

Worktrees always created from main (unless specified)
Worktrees stored in .worktrees/ directory
Branch name becomes worktree name
.gitignore automatically managed

Safety First

Confirms before creating worktrees
Confirms before cleanup to prevent accidental removal
Won't remove current worktree
Clear error messages for issues

Integration with Workflows

`/ce:review`

Instead of always creating a worktree:

1. Check current branch
2. If ALREADY on target branch (PR branch or requested branch) → stay there, no worktree needed
3. If DIFFERENT branch than the review target → offer worktree:
   "Use worktree for isolated review? (y/n)"
   - yes → call git-worktree skill
   - no → proceed with PR diff on current branch

`/ce:work`

Always offer choice:

1. Ask: "How do you want to work?
   1. New branch on current worktree (live work)
   2. Worktree (parallel work)"

2. If choice 1 → create new branch normally
3. If choice 2 → call git-worktree skill to create from main

Troubleshooting

"Worktree already exists"

If you see this, the script will ask if you want to switch to it instead.

"Cannot remove worktree: it is the current worktree"

Switch out of the worktree first (to main repo), then cleanup:

cd $(git rev-parse --show-toplevel)
bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh cleanup

Lost in a worktree?

See where you are:

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh list

.env files missing in worktree?

If a worktree was created without .env files (e.g., via raw git worktree add), copy them:

bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh copy-env feature-name

Navigate back to main:

cd $(git rev-parse --show-toplevel)

Technical Details

Directory Structure

.worktrees/
├── feature-login/          # Worktree 1
│   ├── .git
│   ├── app/
│   └── ...
├── feature-notifications/  # Worktree 2
│   ├── .git
│   ├── app/
│   └── ...
└── ...

.gitignore (updated to include .worktrees)

How It Works

Uses git worktree add for isolated environments
Each worktree has its own branch
Changes in one worktree don't affect others
Share git history with main repo
Can push from any worktree

Performance

Worktrees are lightweight (just file system links)
No repository duplication
Shared git objects for efficiency
Much faster than cloning or stashing/switching

Weekly Installs

280

Repository

everyinc/compou…g-plugin

GitHub Stars

10.9K

First Seen

Jan 21, 2026

Security Audits

Gen Agent Trust HubWarn SocketPass SnykWarn

Installed on

opencode243

codex241

gemini-cli236

claude-code236

github-copilot221

cursor219

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

140,500 周安装

Git Worktree 管理器 - 高效并行开发与代码审查工具，支持自动环境配置

🇨🇳中文介绍

Git Worktree 管理器

此技能的功能

重要提示：始终使用管理器脚本

相关 Skills

何时使用此技能

使用方法

在 Claude Code 工作流中

手动使用

命令

create <branch-name> [from-branch]

list 或 ls

switch <name> 或 go <name>

cleanup 或 clean

工作流示例

使用工作树进行代码审查

并行功能开发

关键设计原则

KISS（保持简单）

约定优于配置

安全第一

与工作流的集成

/ce:review

/ce:work

故障排除

"工作树已存在"

"无法移除工作树：它是当前工作树"

在工作树中迷失了方向？

工作树中缺少 .env 文件？

技术细节

目录结构

工作原理

性能

🇺🇸English

Git Worktree Manager

What This Skill Does

CRITICAL: Always Use the Manager Script

When to Use This Skill

How to Use

In Claude Code Workflows

Manual Usage

Commands

create <branch-name> [from-branch]

list or ls

switch <name> or go <name>

cleanup or clean

Workflow Examples

Code Review with Worktree

Parallel Feature Development

Key Design Principles

KISS (Keep It Simple, Stupid)

Opinionated Defaults

Safety First

Integration with Workflows

/ce:review

/ce:work

Troubleshooting

"Worktree already exists"

"Cannot remove worktree: it is the current worktree"

Lost in a worktree?

.env files missing in worktree?

Technical Details

Directory Structure

How It Works

Performance

最新 Skills

`create <branch-name> [from-branch]`

`list` 或 `ls`

`switch <name>` 或 `go <name>`

`cleanup` 或 `clean`

`/ce:review`

`/ce:work`

`create <branch-name> [from-branch]`

`list` or `ls`

`switch <name>` or `go <name>`

`cleanup` or `clean`

`/ce:review`

`/ce:work`