using-git-worktrees

当需要开始与当前工作区隔离的功能开发，或在执行实现计划之前使用——通过原生工具或 git worktree 回退机制确保隔离工作区存在

Quality

71%

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 ./skills/using-git-worktrees/SKILL.md

Quality

Content

81%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 content is a well-structured, highly actionable workflow with explicit validation checkpoints, feedback loops, and a navigable quick-reference table. Its main weaknesses are minor verbosity in the rationalizations section and a couple of incompletely-resolved variables in the creation command.

Suggestions

Tighten or trim the "常见的合理化借口" table and the inline "为什么关键" justifications to lift conciseness toward a 5.

Make the worktree-creation block fully copy-paste ready by resolving $LOCATION and $BRANCH_NAME inline (e.g. showing the chosen .worktrees path and a concrete branch name) so no prior-step variable is left undefined.

Consider extracting the per-language setup matrix or the rationalizations into a short reference file if the skill grows, to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — commands live in code blocks, setup is compact, and a quick-reference table compresses cases. Minor over-explanation remains (the "常见的合理化借口" rationalizations table and a few "为什么关键" justifications) that could be trimmed. Not a 5 because of those padded editorial sections.	4 / 5
Actionability	Concrete, executable bash commands appear throughout (git rev-parse --git-dir/--git-common-dir, git check-ignore, git worktree add "$path" -b "$BRANCH_NAME", per-language setup). Not a 5 because the worktree-creation block leaves $LOCATION/$BRANCH_NAME unresolved in one copy-paste unit and the native-tool branch is descriptive rather than a runnable command.	4 / 5
Workflow Clarity	A clearly sequenced Step 0→1→2→3 workflow with explicit validation checkpoints (check-ignore before creation, baseline test in Step 3), feedback loops (sandbox permission fallback; 'if tests fail, report and ask'), and a quick-reference table acting as a checklist. The risky-state risk (un-ignored worktree dir) is explicitly guarded.	5 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), and the single file is well-organized with clear section headers plus quick-reference and rationalization tables for navigation. Not a 5 because it is a single monolithic file with no one-level-deep reference split, though for this single-purpose workflow skill nothing clearly belongs in a separate file.	4 / 5
	Total	17 / 20 Passed

Description

62%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 explicitly covers both what the skill does and when to use it, with a clear, distinct niche around isolated git worktrees. It is held back by moderate trigger-term coverage and only partially comprehensive action listing.

Suggestions

Add a 'Use when...' clause with more natural trigger phrases users would say, e.g. 'Use when starting feature work that should be isolated from the current branch, running parallel branches, or preparing an isolated workspace before implementing a plan.'

List a few more concrete actions explicitly (detect existing isolation, prefer native worktree tools, fall back to git worktree, verify .gitignore) to lift specificity toward comprehensive coverage.

Include common synonyms (branch isolation, sandbox, parallel branch) alongside 'git worktree' to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the domain (isolated git workspace) and two concrete mechanisms ("原生工具" / "git worktree 回退机制") plus the action "确保隔离工作区存在", but coverage is not comprehensive — detection, preference-checking, and native-tool-first ordering are only implied. Not a 4 because it does not list several specific actions.	3 / 5
Completeness	Both "what" ("通过原生工具或 git worktree 回退机制确保隔离工作区存在") and "when" ("当需要开始与当前工作区隔离的功能开发...在执行实现计划之前使用") are explicitly present with two concrete trigger conditions. Not a 5 because the "when" does not enumerate the fuller set of natural trigger phrases seen in the anchor-5 example.	4 / 5
Trigger Term Quality	Relevant natural terms are present ("功能开发", "工作区隔离", "git worktree"), but common synonyms a user might say (branch isolation, sandbox, parallel branch) are missing, and "在执行实现计划之前" is workflow-specific rather than a broadly natural trigger phrase.	3 / 5
Distinctiveness Conflict Risk	The niche (establishing an isolated git worktree workspace) is clear and specific with distinct triggers, with only minor overlap risk against general git or sandbox skills. Not a 5 because the trigger phrasing is less exhaustive than the anchor-5 example.	4 / 5
	Total	14 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: jnMetaCode/superpowers-zh
Path: skills/using-git-worktrees/SKILL.md
Commit: c68725b

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.