Menu
Create or update Novu environment variables in the user's project safely (never expose the secret key to the client). Complements the official Novu skills by covering project-level env configuration.
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.
Onboard a new DCR OAuth MCP catalog entry with provider-doc vetting and curl probes. Use when adding or changing `mode: dcr` entries in MCP_SERVERS. Abort if the provider requires whitelist or manual approval.
Audits git worktrees and removes the ones that are safe to delete — merged into the base branch (including squash-merges via `gh`), missing on disk, or explicitly confirmed by the user — then deletes the associated local branches and runs `git worktree prune`. Use when the user asks to clean up worktrees, prune worktrees, list stale worktrees, remove merged worktrees or branches, or reclaim disk space from old checkouts.
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).
Build terminal user interfaces (TUIs) using Ink (React for CLIs) and @inkjs/ui with a reactive, session-driven wizard pattern. Use when creating interactive CLI installation wizards, setup flows, or multi-step terminal applications in Node.js/TypeScript. Covers reactive screen resolution, declarative flow pipelines, overlay interrupts, session state management, Ink components, Flexbox terminal layout, and graceful degradation across terminal environments.
Critically triage pull request review comments against PR requirements and codebase reality, implement only valid fixes, and reply only when declining a suggestion. Use when the user asks to address PR comments, review feedback, CodeRabbit/Bugbot threads, or `/address-pr-review`.
| name | env-setup |
| description | Create or update Novu environment variables in the user's project safely (never expose the secret key to the client). Complements the official Novu skills by covering project-level env configuration. |
| triggers | ["configure novu env vars","add novu keys to .env","secret key handling"] |
Apply this skill exactly once per project, before installing client snippets.
| Variable | Where it lives | Purpose |
|---|---|---|
NOVU_SECRET_KEY | Server only | Auth for @novu/api, @novu/framework, MCP, CLI. |
NEXT_PUBLIC_NOVU_APPLICATION_IDENTIFIER (Next.js) / VITE_NOVU_APPLICATION_IDENTIFIER (Vite) / REACT_APP_NOVU_APPLICATION_IDENTIFIER (CRA) | Client | Identifies the Novu application for the Inbox component. |
Optional:
NOVU_API_URL=https://eu.api.novu.co for EU tenants.NEXT_PUBLIC_NOVU_SUBSCRIBER_ID (only for static / demo apps that don't have a real auth provider — never use this in production).NOVU_SECRET_KEY with NEXT_PUBLIC_*, VITE_*, or REACT_APP_*. Doing so leaks it into the client bundle..env.local, .env.example, and (if present) deployment manifests like vercel.json, netlify.toml, or fly.toml..gitignore to ensure .env.local is ignored.@t3-oss/env-nextjs or similar typed env loaders, register the new keys in their schema..env.example contains placeholder entries for every variable above..env.local (or platform-specific equivalent) has real values.console.log or telemetry call prints the secret key.public/, src/components/, or any client bundle entrypoint.