CtrlK
BlogDocsLog inGet started
Tessl Logo

worktree-cleanup

Removes git worktrees safely, cleans up associated branches, and pulls latest mainline after removal. Use when finished with a worktree, done with a branch, cleaning up after a merge or PR, abandoning work in a worktree, or when "git worktree list" shows stale entries. Checks for uncommitted changes, verifies no open PRs before branch deletion, and handles force-removal of locked worktrees.

80

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

This is an excellent skill that is lean, actionable, and well-structured. The critical CWD warning with its recovery procedure is particularly valuable — it addresses a real, non-obvious failure mode that could brick a session. The Red Flags section effectively reinforces safety constraints, and the quick reference table provides efficient lookup.

DimensionReasoningScore

Conciseness

Every section earns its place. No unnecessary explanations of what git worktrees are or how git works. The content focuses entirely on operational details Claude wouldn't inherently know, like the critical CWD issue and the specific command chaining pattern.

3 / 3

Actionability

All commands are fully executable and copy-paste ready with clear placeholders. The skill provides specific bash commands for every step, includes fallback commands, and covers edge cases like locked worktrees, stale metadata, and dead CWD recovery.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (Steps 1-5) with explicit validation checkpoints: checking for uncommitted changes before removal, checking for open PRs before branch deletion, and handling pull failures gracefully. The recovery section for dead CWD is an excellent feedback loop for a common failure mode.

3 / 3

Progressive Disclosure

For a standalone skill with no bundle files, the content is well-organized with clear sections, a quick reference table, and an integration section pointing to related skills. The length is appropriate for the complexity of the task without needing external files.

3 / 3

Total

12

/

12

Passed

Description

100%

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

This is an excellent skill description that clearly articulates specific capabilities (worktree removal, branch cleanup, mainline pulling, safety checks) and provides comprehensive trigger guidance via an explicit 'Use when' clause with multiple natural scenarios. It uses proper third-person voice throughout and is concise yet thorough, making it easy for Claude to select this skill precisely when needed.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: removes worktrees, cleans up branches, pulls latest mainline, checks for uncommitted changes, verifies no open PRs, handles force-removal of locked worktrees.

3 / 3

Completeness

Clearly answers both what (removes worktrees, cleans branches, pulls mainline, checks uncommitted changes, verifies PRs) and when (finished with worktree, done with branch, cleaning up after merge/PR, abandoning work, stale entries) with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'worktree', 'branch', 'cleaning up', 'merge', 'PR', 'git worktree list', 'stale entries', 'abandoning work'. These are terms users would naturally use when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Very distinct niche focused specifically on git worktree removal and cleanup. The combination of worktree management, branch cleanup, and PR verification creates a clear, unique identity unlikely to conflict with general git or branch management skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
shousper/claude-kit
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.