Agent Skills › novuhq/novu › nv-worktree-create

nv-worktree-create

GitHub

创建Git并行工作区，自动新建分支、同步环境变量及企业子模块配置，便于独立开发。

.cursor/skills/nv-worktree-create/SKILL.md novuhq/novu

Trigger Scenarios

用户请求创建工作区(worktree) 使用/worktree命令指定分支名需要并行分支检出

Install

npx skills add novuhq/novu --skill nv-worktree-create -g -y

More Options

Use without installing

npx skills use novuhq/novu@nv-worktree-create

指定 Agent (Claude Code)

npx skills add novuhq/novu --skill nv-worktree-create -a claude-code -g -y

安装 repo 全部 skill

npx skills add novuhq/novu --all -g -y

预览 repo 内 skill

npx skills add novuhq/novu --list

SKILL.md

Frontmatter

{
    "name": "nv-worktree-create",
    "description": "Create a sibling git worktree and a new branch with the same name, copy local `.env*` files, initialize the enterprise submodule, wire enterprise symlinks, and move the agent into the worktree. Use when the user asks for a worktree, parallel branch checkout, or `\/worktree` with a branch name.",
    "disable-model-invocation": true
}

Create a sibling git worktree

Goal: one name → new branch + sibling worktree at ../<name>, ready to work in.

For git command details and path naming, read nv-worktree-commands. For cleanup, read nv-worktree-cleanup.

Inputs

Input	Required	Default
Branch / worktree name	yes — ask if missing	—
Base ref	no	current `HEAD`

Use the name as-is for the git branch. Use the sanitized name for the directory (see nv-worktree-commands).

Steps

Preflight — from the main repo root:
- git rev-parse --show-toplevel
- git worktree list — abort if the target path already exists
- git status --porcelain — if non-empty, warn that the working tree is dirty and ask the user whether to proceed before creating the worktree
Create — always a new branch and worktree:
```
git worktree add -b <branch> <worktree-path> [<base-ref>]
```
Omit <base-ref> to branch from current HEAD.
Copy local env files — from the main checkout into the worktree (gitignored secrets only; not .env.example). Use the rsync recipe in nv-worktree-commands. Report what was copied. Do not run setup-env-files.js — it regenerates encryption keys.
Enterprise submodule — from the worktree root (best-effort; do not block handoff):
- Skip if .source already exists or is linked.
- Prefer linking an existing packages-enterprise clone before submodule init — same candidates as .cursor/scripts/install.sh (sibling ../packages-enterprise, parent checkout .source, /agent/repos/packages-enterprise, etc.).
- Else configure HTTPS git fallback when SSH is unavailable, then shallow-init .source (matches install.sh):
```
git config --global url."https://github.com/".insteadOf "git@github.com:"
gh auth setup-git
git submodule update --init --depth 1 .source
```
- If .source is available, refresh symlinks (warn-only on failure):
```
pnpm symlink:submodules || echo "WARN: symlink:submodules failed; continuing in OSS mode"
```
- If enterprise setup fails, warn and continue in OSS mode — do not block the worktree. For troubleshooting, read enterprise-submodule.
Hand off — move_agent_to_root with the absolute worktree path. Not move_agent_to_cloned_root.
Confirm — branch name, worktree path, base ref, copied env files, enterprise submodule status.

Example

User: /worktree branch=more-dcr-oauths

Branch:     more-dcr-oauths
Path:       ../more-dcr-oauths
Command:    git worktree add -b more-dcr-oauths ../more-dcr-oauths

Then copy .env*, wire .source (link or submodule init) + pnpm symlink:submodules, move_agent_to_root.

Do not

Check out an existing branch — this skill always creates a new branch.
Copy the whole repo — only .env*.
Run pnpm install, pnpm build, or pnpm setup:agent — do those only if the user asks or a task fails.
Symlink node_modules from the parent checkout.
Pick the branch name without the user providing it (or confirming a suggested name).