git-worktree-manager

Run parallel feature work safely with Git worktrees. Standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like an independent local app. Optimized for multi-agent workflows where each agent or terminal session owns one worktree. Use when running multiple feature branches simultaneously, isolating experimental work, or coordinating multi-agent development across the same repo.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering/skills/git-worktree-manager/SKILL.md

Quality

Content

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

The body is well-structured and actionable with strong workflow clarity and real bundle references, though it is somewhat redundant across its many checklist/pitfalls/practices sections and contains a broken README.md reference. Tightening the repeated guidance and fixing or removing the dangling link would lift the weaker dimensions.

Suggestions

Consolidate overlapping guidance: merge Common Pitfalls, Best Practices, Validation Checklist, and Operational Checklist verifications (e.g., dirty-worktree removal, .worktree-ports.json and env-file checks) into a single source to reduce redundancy.

Fix the broken reference: either add a real README.md or remove the [README.md](README.md) link from the References section.

Convert described workflow steps (e.g., "Review generated port map", "Start app using allocated ports") into exact copy-paste commands to push actionability toward fully executable coverage.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's intelligence (no explaining of worktrees or ports) but repeats the same guidance across Common Pitfalls, Best Practices, Validation Checklist, and Operational Checklist (e.g., dirty-worktree removal and port/env verification stated multiple times), so it could be tightened more than minorly.	3 / 5
Actionability	Provides concrete, executable commands with real flags and existing script paths (e.g., `python scripts/worktree_manager.py --repo . --branch feature/new-auth ...`) and specific port values, but a few workflow steps are described rather than given as exact copy-paste commands.	4 / 5
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit validation (Validation Checklist, Operational Checklist Before/After), safety rules for the destructive cleanup operation, and a Failure Recovery section providing validate/fix/retry feedback loops.	5 / 5
Progressive Disclosure	Good structure with well-signaled one-level-deep references to real files (references/docker-compose-patterns.md, references/port-allocation-strategy.md) and logic split into scripts/, but the body references a README.md that does not exist, a minor navigation gap.	4 / 5
	Total	16 / 20 Passed

Description

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

The description is strong: it clearly states both what the skill does and when to use it, with a concrete "Use when..." clause and a distinct, low-conflict niche. Minor gaps in specificity and trigger-term comprehensiveness keep specificity and trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("Standardizes branch isolation, port allocation, environment sync, and cleanup"), but the actions are stated abstractly rather than as discrete concrete verbs, leaving minor coverage gaps versus the comprehensive 5 anchor.	4 / 5
Completeness	Explicitly answers both what ("Run parallel feature work safely... Standardizes branch isolation, port allocation, environment sync, and cleanup") and when with a concrete "Use when..." clause listing three trigger scenarios, matching the 5 anchor.	5 / 5
Trigger Term Quality	Good natural-term coverage ("Git worktrees", "running multiple feature branches", "isolating experimental work", "coordinating multi-agent development"), but a few natural phrasings and synonym variations are missing versus the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (Git worktrees for parallel/multi-agent branch isolation) with distinct, specific triggers that are unlikely to fire for the wrong skill, matching the 5 anchor.	5 / 5
	Total	18 / 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: engineering/skills/git-worktree-manager/SKILL.md
Commit: 19392f7

Reviewed: ~3 hours 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.