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

91%

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

90%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 clean, executable command reference with strong validation guards for the risky operations and no token waste. Workflow clarity is slightly below perfect because the steps are sectioned rather than given as an explicit ordered sequence with feedback loops.

Dimension	Reasoning	Score
Conciseness	Lean reference that assumes Claude's competence — no explaining what a worktree is or how package managers work; tables and code blocks earn every token.	5 / 5
Actionability	Fully executable commands throughout (git worktree add, rsync include filter, git ls-files loop, lockfile-keyed install table) with clearly marked placeholders covering the common cases.	5 / 5
Workflow Clarity	Section-ordered create→inspect→copy→install→build→remove flow with explicit checkpoints ('Abort if WORKTREE already exists', '--force only when the user explicitly asks'), though presented as a reference rather than a single numbered sequence.	4 / 5
Progressive Disclosure	Well-organized sections with one-level-deep pointers to sibling skills (nv-worktree-cleanup, nv-worktree-create) and no inlined content that belongs elsewhere; no bundle files exist to verify references against.	4 / 5
	Total	18 / 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 tight, specific description that clearly states both the skill's scope and its trigger conditions, plus explicit disambiguation from a related skill. Only minor synonym coverage keeps trigger terms from a perfect score.

Dimension	Reasoning	Score
Specificity	Enumerates six concrete capability areas — 'path naming, create/remove/prune, .env* copy, package-manager install, and cleanup' — tied to a concrete domain, giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated command areas) and 'when' ('Use when implementing or debugging worktree setup'), with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Strong natural terms ('git worktree', 'create/remove/prune', 'worktree setup', 'cleanup') that a user would say, but a few synonyms (plural 'worktrees', 'git work-tree') are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche with explicit boundary guidance ('not as the primary user-facing workflow (see nv-worktree-create)') that actively disambiguates from sibling skills.	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: fc9a0fd

Reviewed: 3 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.