Name: git-worktree-manager
Rating: 61.6 (1 reviews)
Author: alirezarezvani

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

73%

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 ./.gemini/skills/git-worktree-manager/SKILL.md

The canonical home for this skill is git-worktree-manager in alirezarezvani/claude-skills

Quality

Content

60%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 safety-conscious with solid validation flows, but it critically depends on scripts and reference files that are not present in the skill bundle, undermining both actionability and navigation.

Suggestions

Bundle the missing scripts (worktree_manager.py, worktree_cleanup.py) and reference files (port-allocation-strategy.md, docker-compose-patterns.md, README.md) so the documented commands and links resolve.

Consolidate the overlapping Common Pitfalls, Best Practices, and Operational Checklist sections to reduce redundancy and tighten the token budget.

If any referenced file is intentionally external, state where it lives instead of linking to a non-existent relative path.

Dimension	Reasoning	Score
Conciseness	Well-organized with short lists and executable snippets and no padding with concepts Claude already knows, though Common Pitfalls/Best Practices/Operational Checklist and the Validation/After-Creation checklists overlap noticeably and could be consolidated.	4 / 5
Actionability	Provides concrete commands with real flags (e.g. `python scripts/worktree_manager.py --branch feature/new-auth --install-deps`), but the referenced scripts do not exist in the bundle, so the guidance is not actually executable as written.	3 / 5
Workflow Clarity	Sequences are clear with explicit validation checkpoints (Validation Checklist, "Before Removal" verifying merged/uncommitted state, Failure Recovery) and safe-removal gating, satisfying the destructive/batch feedback-loop requirement; minor gaps keep it just below 5.	4 / 5
Progressive Disclosure	References are clearly signaled and one-level-deep in intent, but the targets they point to (`references/port-allocation-strategy.md`, `references/docker-compose-patterns.md`, `README.md`) and the scripts are absent from the bundle, so navigation is broken.	2 / 5
	Total	13 / 20 Passed

Description

87%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 concisely states concrete capabilities and pairs them with an explicit, natural-language "Use when..." trigger clause. Its only weakness is slightly narrower keyword variation than the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "branch isolation, port allocation, environment sync, and cleanup" — making each worktree "an independent local app," with only minor coverage gaps (no mention of dependency install or merged-branch detection).	4 / 5
Completeness	Explicitly answers "what" (standardizes isolation, ports, env sync, cleanup) and "when" via a concrete "Use when running multiple feature branches simultaneously, isolating experimental work, or coordinating multi-agent development" trigger clause.	5 / 5
Trigger Term Quality	Includes natural user-facing phrases like "running multiple feature branches simultaneously," "isolating experimental work," and "coordinating multi-agent development," though it lacks some synonym/file-extension variations that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Git worktrees for multi-agent parallel development) with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 5 missing	Warning
referenced_paths_exist	Referenced path issues: 11 missing	Warning

	Total	14 / 16 Passed

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

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