git-worktrees

Work with git worktrees for isolated parallel development. Use when starting feature work in isolation, when need separate workspace without branch switching, or when cleaning up worktrees after PR merge.

Quality

92%

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

Quality

Content

85%

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

The content is highly actionable with executable commands, clear sequenced workflows, and explicit validation for the destructive removal operations. It is only slightly held back by minor conceptual restating in the overview and dependency-install options.

Suggestions

Trim the Overview's explanation that worktrees share the same .git history; Claude already knows this and it adds tokens without actionable value.

Collapse the "npm install # or pnpm install, yarn" options to a single representative command, since listing every package manager is padding that doesn't change the workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but the Overview re-explains that worktrees "share the same .git history" and the Setup section offers npm/pnpm/yarn alternatives — small amounts of explanatory padding Claude already knows, so it sits between lean and fully tightened.	2 / 3
Actionability	Throughout the document the guidance is concrete and executable — a Quick Reference command table, copy-paste "git worktree add" invocations, and specific cleanup/troubleshooting commands — reaching the top anchor.	3 / 3
Workflow Clarity	The removal and cleanup workflows are numbered with explicit validation checkpoints ("git -C ... status --porcelain", "gh pr list --state merged") plus a Removal Decision Matrix and safe "-d" branch deletion, satisfying the validation-feedback anchor for a destructive operation.	3 / 3
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized into clearly navigable sections (Quick Reference, Creating, Setup, Safety, Cleanup, Patterns, Troubleshooting), appropriate for its scope with no deep reference nesting.	3 / 3
	Total	11 / 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.

The description is concise, concrete, and clearly answers both what the skill does and when to use it, with natural trigger phrasing. It is distinctive and low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Work with git worktrees", "starting feature work in isolation", "separate workspace without branch switching", and "cleaning up worktrees after PR merge" — rather than vague language, matching the top anchor.	3 / 3
Completeness	Explicitly states what the skill does ("Work with git worktrees for isolated parallel development") and an explicit "Use when..." clause enumerating triggers, satisfying both what and when.	3 / 3
Trigger Term Quality	Natural phrasing a user would actually say ("starting feature work", "separate workspace", "cleaning up worktrees", "PR merge", "git worktrees") gives good coverage of common variations, hitting the top anchor.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply defined around git worktrees with distinct triggers unlikely to collide with other skills, so the top anchor applies.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: heyitsnoah/claudesidian
Path: .agents/skills/git-worktrees/SKILL.md
Commit: 6c56f35

Reviewed: about 15 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.