How do I install the Nv Worktree Create skill?

Run npx skillmds@latest add novuhq/nv-worktree-create in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nv Worktree Create safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nv Worktree Create?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nv Worktree Create free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nv Worktree Create?

novuhq (@novuhq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nv Worktree Create by novuhq — Agent Skill

Name: Nv Worktree Create
Author: novuhq

Nv Worktree Create

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.

novuhq 2597061 3.4 KB Updated Sep 17, 2026

File contents

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).

---name: nv-worktree-createdescription: 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.---# 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`).## Steps1. **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 worktree2. **Create** — always a **new** branch and worktree: ```bash git worktree add -b <branch> <worktree-path> [<base-ref>] ``` Omit `<base-ref>` to branch from current `HEAD`.3. **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.4. **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`): ```bash 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): ```bash 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`.5. **Hand off** — `move_agent_to_root` with the absolute worktree path. Not `move_agent_to_cloned_root`.6. **Confirm** — branch name, worktree path, base ref, copied env files, enterprise submodule status.## ExampleUser: `/worktree branch=more-dcr-oauths````textBranch: more-dcr-oauthsPath: ../more-dcr-oauthsCommand: 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).

Frequently asked questions