nv-worktree-commands

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

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-built command reference: fully executable commands, explicit pre/post validation around the risky env-copy and remove steps, and tight section organization. Weaknesses are minor — some already-known content (lockfile table) and reference-style rather than sequenced workflow presentation.

Suggestions

Trim or drop the lockfile-to-package-manager table (or reduce it to one line like 'install with the lockfile's matching package manager') — Claude already knows this mapping.

Add a short numbered lifecycle overview at the top (naming → create → copy env → install → build → remove) so the reference sections read as an ordered workflow with explicit checkpoints.

Consider moving the Novu-specific env-copy notes into a reference file if the skill grows, keeping SKILL.md a lean general reference.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, purposeful code blocks and tables, but includes minor over-explanation of things Claude already knows — e.g. the lockfile-to-installer table ('pnpm-lock.yaml → pnpm install') — and a slightly long exclude list in the rsync command. Fits 'efficient; minor instances of over-explanation' (4) rather than the every-token-earns-its-place of 5.	4 / 5
Actionability	Everything is executable: concrete `git worktree add -b` forms with base-ref options, a copy-paste rsync command, a runnable shell-loop fallback, an explicit abort precondition, and a post-copy verification `find` command — copy-paste ready covering the common cases.	5 / 5
Workflow Clarity	Sections follow a coherent lifecycle (naming → create → inspect → env copy → install → build → remove) and include real checkpoints ('Abort if `WORKTREE` already exists on disk or in `git worktree list`', 'After copying, list what landed', '--force only when the user explicitly asks'), so the destructive-operation cap does not apply. Not 5 because it is organized as reference sections rather than an explicit sequence, leaving some checkpoints implicit.	4 / 5
Progressive Disclosure	No bundle files exist and the body is well organized with clearly signaled cross-references to sibling skills (`nv-worktree-create`, `nv-worktree-cleanup`) rather than buried references, and no content obviously belongs in a separate file. It does not hit 5 because nothing is offloaded at all — the skill exceeds 50 lines with everything inline, so there is no disclosure structure to reward.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete action list, explicit use-when trigger, third-person voice, and explicit boundary guidance against a sibling skill. The only gap is limited trigger synonym coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — 'path naming, create/remove/prune, `.env*` copy, package-manager install, and cleanup' — giving comprehensive coverage of the command reference's scope, matching the top anchor rather than the 'minor gaps' of a 4.	5 / 5
Completeness	It explicitly answers both: the 'what' ('Git worktree command reference: path naming, create/remove/prune, `.env*` copy, package-manager install, and cleanup') and a concrete 'when' ('Use when implementing or debugging worktree setup'), matching the anchor-5 pattern of a clear what plus an explicit trigger phrase.	5 / 5
Trigger Term Quality	'git worktree', 'worktree setup', and 'implementing or debugging' are natural terms a user would say, but coverage stops there — no synonyms or phrasing variations like 'create a worktree' or 'parallel branch checkout', so a few natural terms are missing (anchor 4).	4 / 5
Distinctiveness Conflict Risk	'Worktree' is a distinctive niche trigger, and the description actively de-conflicts by stating it is 'not as the primary user-facing workflow (see nv-worktree-create)', minimizing the risk of triggering for the wrong sibling skill.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: novuhq/novu
Path: .cursor/skills/nv-worktree-commands/SKILL.md
Commit: 320a0ce

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.