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.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/git/skills/git-worktrees/SKILL.md

Quality

Content

63%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.

Highly actionable content with concrete commands and clear workflows, but it suffers from severe length and duplication — the same compare/merge/cherry-pick material is repeated across multiple inlined sections rather than split into separate reference files.

Suggestions

Split the three large 'How to Compare/Create/Merge Worktree' workflows into separate reference files (e.g. references/compare.md, create.md, merge.md) and surface them as one-level-deep links from a concise SKILL.md overview to fix progressive disclosure and reduce duplication.

De-duplicate the selective-merge and cherry-pick material, which currently appears in both the 'Comparing and Merging Changes Between Worktrees' section and again in the 'How to Merge Worktree' section.

Add an explicit validation checkpoint before destructive 'git worktree remove --force' calls in each Pattern workflow (e.g. verify clean status) to close the workflow_clarity gap.

Dimension	Reasoning	Score
Conciseness	At ~1360 lines the body is noticeably verbose with several padded, duplicated sections — selective merge/cherry-pick/compare material appears three or more times across 'Comparing and Merging Changes Between Worktrees' and the three inlined 'How to…' workflows, and the Quick Reference table repeats Essential Commands.	2 / 5
Actionability	Fully executable, copy-paste-ready commands and complete workflow examples throughout — 'git worktree add ../feature-x feature-x', full create/compare/merge sequences — covering the common cases concretely.	5 / 5
Workflow Clarity	Clear numbered sequences with validation checkpoints (state checks via git worktree list/git status), Troubleshooting feedback loops, and a Verification Checklist, but individual Pattern workflows skip validation before destructive 'git worktree remove' operations.	4 / 5
Progressive Disclosure	No bundle files exist and the entire skill is a monolithic single file with three large 'How to…' sub-workflows inlined that clearly belong as separate reference files; section headers provide some structure but there is no one-level-deep external navigation.	3 / 5
	Total	14 / 20 Passed

Description

96%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.

A strong, well-constructed description that explicitly covers what the skill does and when to use it with concrete, natural trigger phrases. The only soft spot is minor overlap risk with general git branching skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and scenarios — 'context switching without stashing', 'reviewing PRs while developing', 'testing in isolation', 'comparing implementations across branches' — plus the core capability of providing 'git worktree commands and workflow patterns', giving comprehensive coverage.	5 / 5
Completeness	Explicitly 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...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms a user would say — 'multiple branches simultaneously', 'context switching', 'stashing', 'reviewing PRs', 'comparing implementations', and the core 'git worktree' keyword — covering several scenario synonyms.	5 / 5
Distinctiveness Conflict Risk	The git worktree niche is distinct with specific triggers, but phrases like 'context switching' and 'switching without stashing' carry minor overlap risk with general git branching/stashing skills.	4 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 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	15 / 16 Passed

Repository: NeoLabHQ/context-engineering-kit
Path: plugins/git/skills/git-worktrees/SKILL.md
Commit: 8539779

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