New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Nv Worktree Commands

by novuhq in novuhq/novu

Git worktree command reference: path naming, create/remove/prune, .env copy, package-manager install, and cleanup.

Custom licenceAuto-check: notesDevelopment

Install Nv Worktree Commands

skills CLI
$ npx skills add novuhq/novu --skill nv-worktree-commands -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install novuhq/novu nv-worktree-commands --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/novuhq/novu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/nv-worktree-commands .claude/skills/nv-worktree-commands && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nv-worktree-commands
GitHub stars
40k
Token cost
~1k tokens
SKILL.md length
285 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
Custom licence

At a glance

Git worktree command reference: path naming, create/remove/prune, .env copy, package-manager install, and cleanup.

  • Debugging worktree setup — not as the primary user-facing workflow (see nv-worktree-create)
  • SKILL.md covers Path naming, Create (new branch), Inspect and Copy local env files, plus 4 more sections
  • Calls git, pnpm and rsync; needs STORE_ENCRYPTION_KEY
  • Tasks that involve Git worktrees

What it does

Nv Worktree Commands is an agent skill from novuhq/novu. Git worktree command reference: path naming, create/remove/prune, .env copy, package-manager install, and cleanup. Use when implementing or debugging worktree setup — not as the primary user-facing workflow (see nv-worktree-create).

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git worktrees. It works with Git. The repository describes itself as: The open-source communication infrastructure for agents and products.

When your agent uses it

  • Debugging worktree setup — not as the primary user-facing workflow (see nv-worktree-create)
  • Tasks that involve Git worktrees

Example prompts

  • “/nv-worktree-commands”

Requirements

  • Node.js
  • A credential in STORE_ENCRYPTION_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit 8a05b88. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • pnpm
    • rsync
    • node
    • yarn
    • npm
    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, pnpm, rsync, yarn and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • STORE_ENCRYPTION_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nv Worktree Commands loads about 1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:4
    ence: path naming, create/remove/prune, `.env*`
  • NoteMentions a .env fileSKILL.md:67
    --include='.env' \
  • NoteMentions a .env fileSKILL.md:68
    --include='.env.*' \
  • NoteMentions a .env fileSKILL.md:88
    .env|.env.*)
  • NoteMentions a .env fileSKILL.md:99
    `find <worktree-path> -type f \( -name '.env' -o -name '.env.*' \) ! -name '.env.example' ! -name '.env.template'`).
  • NoteMentions a .env fileSKILL.md:103
    s a **new** `STORE_ENCRYPTION_KEY` when `.env` is missing — a worktree would then disagree with the parent and shared lo
  • NoteMentions a .env fileSKILL.md:104
    - Typical files copied: `apps/api/src/.env`, `.env.agent`, `.env.development`, `apps/dashboard/.env`, `apps/worker/src/.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 285 words (~1,002 tokens).

“Reference for agents implementing worktree workflows. Prefer nv-worktree-create for the end-to-end flow.”

— opening of SKILL.md by novuhq, Custom licence
name
nv-worktree-commands

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .cursor/skills/nv-worktree-commands of novuhq/novu.

Open the folder on GitHubat commit 8a05b88

Compare with similar skills

Nv Worktree Commands next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nv Worktree Commands compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nv Worktree Commands this skillnovuhq/novu40k—~1kAutomated safety check: NotesCustom licence
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT
Git Worktree Cleanuplobehub/lobehub83k—~2.8kAutomated safety check: PassCustom licence
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Ccmanager Configkbwo/ccmanager1.3k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Finishing A Development Branch

    farm-fe/farm

    A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed

  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Ccmanager Config

    kbwo/ccmanager

    Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.

    1.3k GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Cap Feature Building Workflow

    CapSoftware/Cap

    Builds a Cap feature in an isolated Git worktree with disposable dev resources, verification, a recorded demo and a neutral pull request, started with /building.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: warnings

More from novuhq/novu

All 28 skills in this repo

  • Ink Tui Wizard

    novuhq/novu

    Build terminal user interfaces (TUIs) using Ink (React for CLIs) and @inkjs/ui with a reactive, session-driven wizard pattern.

    40k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Novu Design Workflow

    novuhq/novu

    Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state.

    40k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Novu Inbox Integration

    novuhq/novu

    Integrate Novu's in-app notification inbox into web applications.

    40k GitHub stars~5.2k tokensUpdated today
    Auto-check passed

  • Novu Manage Preferences

    novuhq/novu

    Configure notification preferences in Novu at the workflow and subscriber level.

    40k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Novu Manage Subscribers

    novuhq/novu

    Create, update, search, and delete subscribers in Novu. An agent skill from novuhq/novu.

    40k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Novu Trigger Notification

    novuhq/novu

    Trigger Novu notification workflows to send messages across email, SMS, push, chat, and in-app channels.

    40k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Nv Worktree Commands

What does Nv Worktree Commands do?

Git worktree command reference: path naming, create/remove/prune, .env copy, package-manager install, and cleanup. Nv Worktree Commands is an agent skill from novuhq/novu.env copy, package-manager install, and cleanup.

When should I use Nv Worktree Commands?

Nv Worktree Commands fits situations like: debugging worktree setup — not as the primary user-facing workflow (see nv-worktree-create); tasks that involve Git worktrees.

How do I install Nv Worktree Commands in Claude Code?

Run `npx skills add novuhq/novu --skill nv-worktree-commands -a claude-code`. Or copy the skill folder (.cursor/skills/nv-worktree-commands in novuhq/novu) into .claude/skills/nv-worktree-commands in your project. Claude Code loads it when a task matches its description.

How do I install Nv Worktree Commands in Codex?

Run `npx skills add novuhq/novu --skill nv-worktree-commands -a codex`. Or copy the skill folder (.cursor/skills/nv-worktree-commands in novuhq/novu) into .agents/skills/nv-worktree-commands in your project. Codex loads it when a task matches its description.

Can I use Nv Worktree Commands in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add novuhq/novu --skill nv-worktree-commands -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nv-worktree-commands, .gemini/skills/nv-worktree-commands, .github/skills/nv-worktree-commands and .opencode/skills/nv-worktree-commands in your project.

What does Nv Worktree Commands need to run?

Going by SKILL.md and its folder, Nv Worktree Commands needs the command-line tools its instructions call (git, pnpm, rsync, node, yarn and npm) and credentials named STORE_ENCRYPTION_KEY. Our summary lists: Node.js; A credential in STORE_ENCRYPTION_KEY.

Does Nv Worktree Commands access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nv Worktree Commands safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Nv Worktree Commands use?

Nv Worktree Commands has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Nv Worktree Commands use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nv Worktree Commands?

Skills that share tags, products or a category with Nv Worktree Commands: Finishing a Development Branch (obra/superpowers, 297k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars), Git Worktree Cleanup (lobehub/lobehub, 83k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nv Worktree Commands?

novuhq (a GitHub organization) maintains it in novuhq/novu, which has 40,134 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 2026.

Source: novuhq/novu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.