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

76%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/using-git-worktrees/SKILL.md

Quality

Content

77%

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

This is a well-crafted skill with strong actionability and workflow clarity — every step has executable commands and validation checkpoints are explicit with error recovery paths. The main weaknesses are moderate redundancy between the Quick Reference, Common Mistakes, and Red Flags sections, and the content is somewhat long for a single file without supporting bundle files to offload secondary details.

Suggestions

Remove or consolidate the 'Red Flags' section since it largely duplicates guidance already covered in 'Common Mistakes' and the Quick Reference table.

Remove the opening sentence explaining what git worktrees are — Claude already knows this.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but has some redundancy — the 'Red Flags' section largely repeats the 'Common Mistakes' section and the Quick Reference table. The 'Overview' section's explanation of what worktrees are is unnecessary for Claude. Some sections could be tightened.	2 / 3
Actionability	Provides fully executable bash commands throughout, with concrete code for every step: directory detection, gitignore verification, worktree creation, project setup auto-detection, and test verification. The commands are copy-paste ready and cover multiple project types.	3 / 3
Workflow Clarity	The multi-step process is clearly sequenced (directory selection → safety verification → creation → setup → test baseline → report). Explicit validation checkpoints exist: git check-ignore verification, test baseline verification with failure handling, and the SQLite delegation has a clear failure contract with exit code checking.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and a quick reference table, but it's quite long for a single file with no bundle files to offload detail into. The setup commands for multiple project types and the common mistakes section could potentially be split out. References to other skills (using-sqlite-worktrees, finishing-a-development-branch) are clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 has strong completeness with explicit 'Use when' triggers and a clear niche that minimizes conflict risk. However, it could benefit from more specific concrete actions beyond just 'creates' and better coverage of natural trigger terms users might use when they need worktree functionality.

Suggestions

List additional concrete actions such as 'creates worktrees, sets up branches, configures directory structure' to improve specificity.

Add more natural trigger terms users might say, such as 'worktree', 'parallel branch', 'separate working directory', or 'git worktree add'.

Dimension	Reasoning	Score
Specificity	Names the domain (git worktrees) and some actions ('creates isolated git worktrees with smart directory selection and safety verification'), but doesn't list multiple concrete actions beyond creation. Missing specifics like branch creation, linking, cleanup, etc.	2 / 3
Completeness	Explicitly answers both what ('creates isolated git worktrees with smart directory selection and safety verification') and when ('when starting feature work that needs isolation from current workspace or before executing implementation plans') with clear trigger conditions.	3 / 3
Trigger Term Quality	Includes relevant terms like 'git worktrees', 'feature work', 'isolation', 'workspace', and 'implementation plans', but misses common user phrases like 'worktree', 'branch', 'parallel development', 'separate directory', or 'git worktree add'.	2 / 3
Distinctiveness Conflict Risk	Git worktree creation is a very specific niche that is unlikely to conflict with other skills. The triggers ('feature work that needs isolation', 'implementation plans', 'worktrees') are distinct and narrowly scoped.	3 / 3
	Total	10 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: lucianghinda/superpowers-ruby
Commit: 712d734

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