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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

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.

A well-structured operational skill with executable commands at every step, explicit validation and recovery checkpoints for destructive operations, and clean section-based organization. It assumes Claude's intelligence and earns its length through real gotchas rather than concept explanation.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — it never explains git/worktree concepts — and every section earns its place; the repeated 'cd <main-working-tree> &&' chaining rule is deliberate safety emphasis for a footgun rather than filler, matching the lean score-3 anchor and staying above the score-2 'could be tightened' bar.

3 / 3

Actionability

Every step gives fully executable, copy-paste-ready commands with concrete flags (e.g. 'git -C <worktree-path> status --porcelain', 'gh pr list --head <branch-name> --state open --json number --jq length'), matching the score-3 anchor with no pseudocode or missing details that would drop it to score 2.

3 / 3

Workflow Clarity

Steps 1–5 form a clear sequence with explicit validation checkpoints (uncommitted-change check, open-PR check before branch deletion) and a 'Recovery: Dead CWD' feedback loop, plus a Red Flags Never/Always checklist — matching the score-3 anchor for destructive operations rather than the checkpoint-gap score 2.

3 / 3

Progressive Disclosure

As a single-file skill with no bundle files, it is well-organized into clear sections (Overview, Process, Red Flags, Quick Reference, Integration) with easy navigation and nothing that obviously belongs in a separate file, satisfying the well-organized-sections path to score 3 rather than the inline-bloat score 2.

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.

A strong description that states concrete capabilities, provides explicit natural-language triggers, answers both what and when, and is narrowly scoped to worktree cleanup. Uses correct third-person voice throughout with no first/second-person phrasing.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'Removes git worktrees safely, cleans up associated branches, and pulls latest mainline' plus 'Checks for uncommitted changes, verifies no open PRs before branch deletion, and handles force-removal of locked worktrees' — matching the score-3 anchor for comprehensive concrete actions, not the partial coverage of score 2.

3 / 3

Completeness

It explicitly answers both 'what' (removes worktrees, cleans branches, pulls mainline) and 'when' via a detailed 'Use when...' clause with explicit triggers, matching the score-3 anchor; it is not score 2 because the 'when' is explicit rather than missing or implied.

3 / 3

Trigger Term Quality

The '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' clause covers natural phrasings a user would actually say, satisfying the score-3 anchor rather than the incomplete keyword coverage of score 2.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche — worktree cleanup — with distinct triggers like 'git worktree list shows stale entries', making it unlikely to fire for unrelated git skills, matching the score-3 anchor rather than the overlap-prone score 2.

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.

Validation16 / 16 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.