using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Quality

81%

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 content is a tightly structured, executable workflow with strong validation checkpoints and feedback loops appropriate to potentially destructive worktree operations. Its main weaknesses are minor placeholder variables that are not fully defined inline and some redundancy between the prose and the summary tables.

Suggestions

Define $LOCATION and $BRANCH_NAME concretely (e.g., show the explicit assignment from the chosen directory and the current branch) so the worktree creation commands are fully copy-paste ready.

Trim redundancy between the Quick Reference / Common Rationalizations tables and the inline step prose to improve token efficiency.

Consider whether the Common Rationalizations table belongs in a separate reference file to bring the main body closer to a lean overview, which would also improve progressive_disclosure toward a 5.

Dimension	Reasoning	Score
Conciseness	Quotes: 'Detect existing isolation first. Then use native tools. Then fall back to git.' — the prose is largely lean and command-driven without explaining git basics, though the Quick Reference and Common Rationalizations tables overlap somewhat with inline prose, keeping it at anchor 4 rather than 5.	4 / 5
Actionability	Quotes: 'git worktree add "$path" -b "$BRANCH_NAME"' and 'git check-ignore -q .worktrees' give mostly executable commands, but $LOCATION and $BRANCH_NAME are referenced without being concretely assigned inline, a minor gap matching anchor 4.	4 / 5
Workflow Clarity	Quotes: Step 0 detection with submodule guard, 'MUST verify directory is ignored before creating worktree', and 'If tests fail: Report failures, ask whether to proceed' show a clear sequence with explicit validation steps, feedback loops, and a Quick Reference checklist matching anchor 5.	5 / 5
Progressive Disclosure	The body is well-organized into Overview, Steps 0-3, Quick Reference, and Common Rationalizations with clear headers and no nested external references; at ~165 lines it is appropriately self-contained but exceeds the under-50-line exception for a 5, so anchor 4 fits best.	4 / 5
	Total	17 / 20 Passed

Description

82%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 explicitly answers both what it does and when to use it, with a clear, distinct niche around workspace isolation. It is strong overall, with the only soft spot being that the concrete actions are named at a high level rather than enumerated in detail.

Dimension	Reasoning	Score
Specificity	Quotes: 'ensures an isolated workspace exists via native tools or git worktree fallback' names the domain and 1-2 concrete mechanisms but does not enumerate several specific actions, matching anchor 3 rather than anchor 4.	3 / 5
Completeness	Quotes: 'ensures an isolated workspace exists via native tools or git worktree fallback' (what) and 'Use when starting feature work that needs isolation... or before executing implementation plans' (when) explicitly answer both with concrete triggers, matching anchor 5.	5 / 5
Trigger Term Quality	Quotes: 'starting feature work', 'isolation from current workspace', 'before executing implementation plans' provide good natural keyword coverage a user would say, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Quotes: 'git worktree fallback', 'native tools', 'isolated workspace' define a clear niche with distinct triggers and minimal overlap with other skills, matching anchor 5.	5 / 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: obra/superpowers
Path: skills/using-git-worktrees/SKILL.md
Commit: b36e082

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