using-git-worktrees
tessl i github:obra/superpowers --skill using-git-worktreesUse 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
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
77%This is a well-crafted skill with excellent actionability and workflow clarity. The step-by-step process with explicit validation checkpoints (gitignore verification, test baseline) demonstrates good safety practices. Minor improvements could be made by reducing redundancy between sections and potentially splitting reference material into separate files.
Suggestions
Remove the Quick Reference table or Common Mistakes section to reduce redundancy - the main workflow sections already cover this information clearly
Consider moving the Common Mistakes and Red Flags sections to a separate TROUBLESHOOTING.md file to reduce the main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some redundancy - the quick reference table duplicates information from the main sections, and the 'Common Mistakes' section restates guidance already covered. The example workflow at the end adds value but could be more compact. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout, with concrete examples for directory checking, worktree creation, project setup detection, and test verification. Commands are copy-paste ready with clear variable placeholders. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints: verify ignored status before creation, run setup, verify clean test baseline, and explicit handling for test failures ('Report failures, ask whether to proceed'). Clear feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in a single file. The 'Integration' section references other skills but the skill itself is somewhat long (~180 lines) and could benefit from separating the quick reference or common mistakes into linked files. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
75%This description effectively communicates when to use the skill with a clear 'Use when...' clause upfront, and establishes a distinct niche around git worktrees. However, it could benefit from more specific concrete actions and additional natural trigger terms that users might actually say when needing this functionality.
Suggestions
Add more specific concrete actions like 'creates worktree directories, sets up branch tracking, validates repository state'
Include additional natural trigger terms users might say: 'parallel development', 'separate workspace', 'work on multiple branches', 'git worktree'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git worktrees) and some actions ('creates isolated git worktrees', 'smart directory selection', 'safety verification'), but lacks comprehensive concrete actions like what specific operations are performed during creation or what safety checks are done. | 2 / 3 |
Completeness | Clearly 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 explicit trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'feature work', 'worktrees', 'implementation plans', but misses common variations users might say like 'branch', 'parallel development', 'separate workspace', or 'git worktree' as a phrase. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on git worktrees for feature isolation, with distinct triggers ('worktrees', 'isolation from current workspace', 'implementation plans') that are unlikely to conflict with general git or branching skills. | 3 / 3 |
Total | 10 / 12 Passed |
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.