using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Quality

82%

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

81%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.

The body is highly actionable with executable commands, explicit validation, and feedback loops that meet the destructive/batch-operation bar. Its weaknesses are moderate redundancy across the Common Mistakes and Red Flags sections and a lack of file-based progressive disclosure for a 247-line skill.

Suggestions

Consolidate the Common Mistakes and Red Flags sections, which restate the ignore-verification and test-baseline guidance already in Safety Verification, to remove redundancy.

Trim the Overview sentence explaining what a git worktree is, since Claude already knows this; lead with the core principle instead.

Consider moving the multi-language setup matrix and the Integration (called-by/pairs-with) block into a reference file to better practice progressive disclosure for a skill of this length.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but the Overview explains what a git worktree is (which Claude already knows) and the Common Mistakes and Red Flags sections substantially restate guidance already covered in Safety Verification and Directory Selection.	3 / 5
Actionability	Copy-paste-ready bash throughout — `git check-ignore`, `git worktree add`, the `case` path resolver, and per-language setup (Rails/Node/Rust/Python/Go) with a concrete SQLite delegation block — covers the common cases fully.	5 / 5
Workflow Clarity	Clear sequenced process (Directory Selection → Safety Verification → Creation Steps 1–5) with explicit validation checkpoints (check-ignore, clean test baseline), feedback loops (test fail → ask; SQLite fail → halt), and a Quick Reference checklist.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with easy in-file navigation, but at ~247 lines everything is inlined in SKILL.md with no bundle files or one-level-deep references to offload the per-language setup matrix or integration details.	4 / 5
	Total	17 / 20 Passed

Description

83%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.

The description cleanly answers both what the skill does and when to use it, with concrete trigger phrases and a distinct worktree-creation niche. The main weaknesses are the mild buzzword 'smart directory selection' and overlap risk on the broad 'before executing implementation plans' trigger.

Suggestions

Drop the buzzword 'smart' from 'smart directory selection' in favor of a concrete phrase like 'priority-based directory selection' to strengthen specificity.

Narrow the 'before executing implementation plans' trigger or qualify it (e.g., 'before executing implementation plans that need an isolated branch') to reduce overlap with executing-plans-style skills.

Add a natural synonym such as 'isolated branch' or 'work on a separate branch' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'creates isolated git worktrees', 'directory selection', 'safety verification' — though 'smart' is mildly fluffy and coverage of the safety/selection mechanics is implied rather than enumerated.	4 / 5
Completeness	Explicitly answers both: WHAT ('creates isolated git worktrees with smart directory selection and safety verification') and WHEN ('Use when starting feature work that needs isolation... or before executing implementation plans') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'starting feature work', 'needs isolation from current workspace', and 'before executing implementation plans' are present, but it misses common synonyms a user might say such as 'branch' or 'work on a separate branch'.	4 / 5
Distinctiveness Conflict Risk	Git worktree creation is a clear niche, but the broad trigger 'before executing implementation plans' overlaps with related workflow skills (executing-plans, subagent-driven-development) that also gate on plan execution.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: lucianghinda/superpowers-ruby
Path: skills/using-git-worktrees/SKILL.md
Commit: 99fac3d

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