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

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

55%

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

The skill is highly actionable with excellent executable examples and well-structured workflows with proper validation checkpoints. However, it is severely undermined by extreme verbosity and redundancy — the same commands (git checkout, cherry-pick, diff) are explained 3-4 times across different sections. The entire document should be split into separate files (COMPARE.md, CREATE.md, MERGE.md) with a lean overview in SKILL.md, which would dramatically improve both conciseness and progressive disclosure.

Suggestions

Split the three sub-workflows (Compare, Create, Merge) into separate referenced files and keep SKILL.md as a concise overview with the Quick Reference table and brief workflow patterns only.

Eliminate redundant command explanations — git checkout, cherry-pick, and diff commands are each explained 3-4 times across sections. Define them once and reference that definition.

Remove the 'Core Concepts' table explaining what a worktree is and what shared .git means — Claude already knows these Git concepts. Focus only on the specific commands and workflow patterns.

Consolidate the 'Common Issues', 'Common Mistakes', and per-section 'Troubleshooting' into a single troubleshooting reference, ideally in a separate file.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 700+ lines with massive redundancy. The 'Comparing and Merging Changes Between Worktrees' section repeats content already covered in the Quick Reference table and Workflow Patterns. The three sub-skills (Compare, Create, Merge) duplicate commands and concepts from the main skill extensively. Multiple sections explain the same git checkout, cherry-pick, and diff commands repeatedly.	1 / 3
Actionability	Every command is fully executable with concrete examples, specific flags, and copy-paste ready bash snippets. The workflow patterns show complete sequences with real commands, and the merge strategies provide step-by-step executable instructions.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit validation steps (checking git status, running git worktree list before operations, verification checklists). The Create workflow includes state checks, dependency detection, and post-creation summaries. The Merge workflow includes pre-merge review, conflict resolution guidance, and cleanup prompts.	3 / 3
Progressive Disclosure	This is a monolithic wall of text with no bundle files to offload content into. The three sub-skills (Compare, Create, Merge) are inlined directly, creating a 700+ line document. These should be separate files referenced from a concise overview. The content structure makes it very difficult to navigate.	1 / 3
	Total	8 / 12 Passed

Description

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 follows best practices. It leads with an explicit 'Use when' clause listing multiple concrete scenarios, uses natural trigger terms users would actually say, and clearly identifies its niche (git worktrees for parallel development). The description is concise yet comprehensive, and uses proper third-person voice.

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') with explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'multiple branches', 'context switching', 'stashing', 'reviewing PRs', 'testing in isolation', 'comparing implementations', 'git worktree', 'parallel development', 'working directories'. These cover a wide range of natural user language.	3 / 3
Distinctiveness Conflict Risk	Clearly carved out niche around git worktrees specifically, which is distinct from general git skills, branching skills, or stashing skills. The focus on 'multiple working directories' and 'parallel development' via worktrees makes it unlikely to conflict with other git-related skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

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 — 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: 3711edf

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