git-worktrees
Use when working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, or comparing implementations across branches - provides git worktree commands and workflow patterns for parallel development with multiple working directories.
76
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/git/skills/git-worktrees/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines both what the skill does and when to use it. It leads with explicit trigger scenarios using natural developer language, then concisely states the capability. The focus on git worktrees creates a clear, distinctive niche that won't overlap with general git skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, comparing implementations across branches, and providing git worktree commands and workflow patterns. | 3 / 3 |
Completeness | Clearly answers both what ('provides git worktree commands and workflow patterns for parallel development with multiple working directories') and when ('Use when working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, or comparing implementations across branches'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'multiple branches', 'context switching', 'stashing', 'reviewing PRs', 'testing in isolation', 'comparing implementations', 'git worktree', 'parallel development', 'working directories'. These are terms developers naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive - git worktree is a specific niche within git workflows. The description clearly differentiates from general git skills by focusing specifically on worktrees, parallel development, and multiple working directories. Unlikely to conflict with general git or branching skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable git worktree guidance with comprehensive coverage of commands, workflow patterns, and troubleshooting. However, it is severely undermined by extreme verbosity and repetition - the same operations (cherry-pick, selective checkout, file comparison, cleanup) are explained 3-4 times across different sections. The monolithic structure with three full sub-workflows inlined makes it very token-inefficient and poorly organized for progressive disclosure.
Suggestions
Split into separate files: a concise SKILL.md overview with quick reference, and separate COMPARE.md, CREATE.md, and MERGE.md files for the detailed sub-workflows, linked from the main file.
Eliminate heavy duplication: the 'Comparing and Merging Changes Between Worktrees' section repeats nearly everything from Pattern 6 and the merge workflow - consolidate into a single location.
Add explicit validation checkpoints to workflows, e.g., after creating a worktree run 'git worktree list' to confirm, after merging run 'git diff --cached' to verify staged changes are correct.
Remove explanations of concepts Claude already knows (e.g., what cherry-pick does, what diff output looks like, basic git concepts) and trim the numerous redundant examples to the most illustrative ones.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The same concepts (cherry-pick, selective checkout, diff between worktrees, cleanup) are explained multiple times across sections. The 'Comparing and Merging Changes Between Worktrees' section heavily duplicates content from Pattern 6 and the merge workflow. The entire document could be reduced by 50-60% without losing information. It also explains basic git concepts Claude already knows. | 1 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout. Every workflow pattern includes concrete bash commands with realistic examples, specific flags, and expected outputs. The interactive patch mode keys table and cherry-pick selective workflow are particularly actionable. | 3 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and specific commands. However, validation checkpoints are mostly missing - the create worktree workflow doesn't verify the worktree was created successfully, the merge workflows lack explicit verification that the merge produced correct results, and there are no feedback loops for error recovery in the main workflows (only troubleshooting sections at the end). | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to reference. Three complete sub-skills (compare, create, merge worktrees) are inlined into a single massive document rather than being split into separate referenced files. The document is extremely long and would benefit enormously from splitting into COMPARE.md, CREATE.md, and MERGE.md with the main SKILL.md serving as an overview with references. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1363 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- NeoLabHQ/context-engineering-kit
- Commit
dedca19
- 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.