CtrlK
BlogDocsLog inGet started
Tessl Logo

nv-worktree-cleanup

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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 high-quality, executable skill body: dense with concrete commands, clear sequencing with validation, and well-structured sections without padding or external-reference indirection.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: no padding or explanations of git concepts Claude already knows; every section (hard rules, workflow, anti-patterns, example) earns its place with concrete commands.

5 / 5

Actionability

Fully executable: exact commands (`git worktree list --porcelain`, `gh pr list --state merged`, `git branch -d/-D`), a concrete classification table with detection commands, and a worked example session — copy-paste ready covering common cases including the `gh`-missing fallback.

5 / 5

Workflow Clarity

Clear 6-step sequence with explicit validation checkpoints (fetch --prune before merge checks, consolidated batch approval via AskQuestion, remove-then-delete-branch ordering) and feedback/anti-pattern guidance for failure modes like squash-merge needing `-D`; the destructive-batch cap does not apply because validation is present.

5 / 5

Progressive Disclosure

No bundle files exist; the single-purpose skill is well-organized into Hard rules, Workflow, Anti-patterns, and Example with no nested references, matching the well-organized-sections exception.

5 / 5

Total

20

/

20

Passed

Description

100%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, specific description that clearly states capabilities and trigger conditions with minimal fluff. It covers the what, when, and distinguishing context comprehensively.

DimensionReasoningScore

Specificity

Names multiple concrete actions — audits, removes worktrees, deletes local branches, runs `git worktree prune` — and enumerates specific safe-to-delete criteria (merged, squash-merge via `gh`, missing on disk, user-confirmed), matching the comprehensive-anchor example.

5 / 5

Completeness

Explicitly answers both 'what' (audit + remove + delete branches + prune) and 'when' via a concrete 'Use when the user asks to...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — 'clean up worktrees', 'prune worktrees', 'list stale worktrees', 'remove merged worktrees or branches', 'reclaim disk space from old checkouts' — giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (git worktree lifecycle cleanup) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
novuhq/novu
Reviewed

Table of Contents

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.