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
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/using-git-worktrees/SKILL.mdQuality
Discovery
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 good structure with an explicit 'Use when' clause and clearly identifies its niche (git worktree creation). However, it could be more specific about the concrete actions it performs beyond 'smart directory selection and safety verification', and could include more natural trigger terms users might use when needing this functionality.
Suggestions
List more concrete actions such as 'creates worktree directories, sets up branches, configures remote tracking' instead of vague phrases like 'smart directory selection'.
Add more natural trigger term variations like 'branch', 'parallel development', 'worktree', 'isolated branch', or 'separate working directory' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'creates isolated git worktrees with smart directory selection and safety verification' which names the domain (git worktrees) and some actions, but doesn't list multiple concrete actions comprehensively - 'smart directory selection' and 'safety verification' are somewhat vague. | 2 / 3 |
Completeness | The description 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 a clear 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'feature work', 'git worktrees', 'implementation plans', and 'workspace', but misses common variations users might say like 'branch', 'parallel development', 'worktree', 'new feature branch', or 'isolated environment'. | 2 / 3 |
Distinctiveness Conflict Risk | Git worktree creation is a very specific niche that is unlikely to conflict with other skills. The triggers around 'feature work isolation' and 'worktrees' are distinct enough to avoid overlap with general git or branching skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
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 strong, actionable skill with excellent workflow clarity — the directory selection priority chain, safety verification with automatic remediation, and baseline test verification form a robust process with proper feedback loops. The main weaknesses are moderate redundancy between the Common Mistakes, Red Flags, and Quick Reference sections (which all cover similar ground), and the document length could be reduced by extracting the multi-language setup detection into a separate reference.
Suggestions
Consolidate the 'Common Mistakes', 'Red Flags', and 'Quick Reference' sections into a single concise reference table to eliminate redundancy
Consider extracting the multi-language project setup detection (Step 3) into a separate referenced file, as it's the longest section and covers 6+ project types
| 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 duplicates logic already explained in the body. The 'Overview' section is lean, but overall the document could be tightened by ~20-30%. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout — directory detection, git check-ignore verification, worktree creation, project setup auto-detection, and test verification are all copy-paste ready with concrete code blocks and specific commands for multiple project types. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced (directory selection → safety verification → creation → setup → test baseline → report) with explicit validation checkpoints: git check-ignore verification before creation, test baseline verification before proceeding, and clear error recovery paths (add to .gitignore if not ignored, report and ask if tests fail, halt if SQLite setup fails). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a fairly long monolithic document (~180 lines of content) with no references to external files for detailed content like the setup scripts or project-type-specific guidance. The Integration section references other skills but the skill itself could benefit from splitting out the project setup detection into a referenced file. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- lucianghinda/superpowers-ruby
- Commit
c037ce3
- 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.