CtrlK
BlogDocsLog inGet started
Tessl Logo

worktree-hygiene

Reap merged git worktrees and branches safely across the warp, codex, opencode, and conductor harnesses. Use when worktrees pile up, after a branch merges, when cleaning up `git worktree list`, removing an orphaned or detached worktree, or deciding whether a worktree is safe to delete. Not for creating branches or authoring commits (use the git skill).

79

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%

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

A tightly written, highly actionable skill body: it skips git basics, gives executable audit/reap commands, sequences a destructive workflow with validation checkpoints, and organizes content cleanly with no nested references.

DimensionReasoningScore

Conciseness

Lean and dense: no generic git concepts are explained, every section delivers commands or decision rules, and tokens go only to non-obvious harness-specific gotchas. It assumes Claude's git competence throughout.

3 / 3

Actionability

Executable, copy-paste-ready commands throughout (the awk audit pipeline, `git merge-base --is-ancestor`, `git worktree remove`, `git branch -d/-D`, `git worktree prune`) with explicit per-condition decision rules in the 'Decide per worktree' block.

3 / 3

Workflow Clarity

Clear audit -> classify -> decide -> reap sequence with explicit validation checkpoints and feedback loops ('Re-run the audit', 'Never reap on a self-reported it's merged', final-checks checklist), well above the destructive-operation bar that would cap at 2.

3 / 3

Progressive Disclosure

The body is self-contained and well-organized into focused sections with no bundle files (references/scripts/assets are absent); for a single-purpose skill under 50 effective lines, well-organized sections earn the top anchor per the simple-skills note.

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, third-person description that names concrete actions, includes natural trigger terms, explicitly states when to use it, and cleanly separates itself from the sibling git skill via a negative-scope clause.

DimensionReasoningScore

Specificity

Multiple concrete actions are named ('Reap merged git worktrees and branches', 'removing an orphaned or detached worktree', 'deciding whether a worktree is safe to delete'), spanning reaping, removal, and the decision procedure.

3 / 3

Completeness

It answers 'what' (reap merged worktrees and branches safely) and 'when' explicitly via the 'Use when...' clause, and additionally scopes out non-use ('Not for creating branches or authoring commits').

3 / 3

Trigger Term Quality

Natural phrases users would say are well covered: 'worktrees pile up', 'after a branch merges', 'cleaning up `git worktree list`', 'orphaned or detached worktree', 'safe to delete'.

3 / 3

Distinctiveness Conflict Risk

The niche is distinct (worktree/branch reaping across four named harnesses) and the negative scope ('Not for creating branches or authoring commits (use the git skill)') sharply separates it from the related git skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
EpicenterHQ/epicenter
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.