dev-worktree

AI DevKit · Worktree setup and resume guidance for isolated feature work. Use when starting, resuming, switching, or verifying a feature branch/worktree for lifecycle, debugging, implementation, review, or multi-agent workflows.

Quality

84%

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

90%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 lean, highly actionable, and well-structured with concrete commands and an explicit verification checkpoint. The only meaningful gap is the absence of an explicit error-recovery feedback loop when context verification fails.

Suggestions

Add a short feedback loop after the step-9 verification (e.g., 'If it does not equal feature-<name>, re-run git worktree add or stop and report') to reach full workflow-clarity maturity.

Consider splitting the long per-ecosystem Dependency Bootstrap command list into a reference file so the SKILL.md overview stays lighter, which would also strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative with no padding or re-explanation of concepts Claude already knows; every line (phase contract, numbered steps, per-ecosystem command lists) earns its place, matching the level-5 anchor.	5 / 5
Actionability	Provides fully executable, copy-paste-ready commands across cases (e.g., 'git worktree add -b feature-<name> .worktrees/feature-<name>', 'npm ci', 'uv sync') with common ecosystems covered, matching the level-5 anchor.	5 / 5
Workflow Clarity	Clear sequenced steps with an approval gate and an explicit verification checkpoint (step 9: branch --show-current 'must equal feature-<name>'), but it lacks an explicit error-recovery feedback loop for what to do when verification fails, sitting just below level 5.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Phase Contract, Start, Resume, Dependency Bootstrap, Output) with no nested references and no bundle files to navigate; at ~68 body lines it is slightly over the under-50-line simple-skill threshold, so it lands at level 4 rather than 5.	4 / 5
	Total	18 / 20 Passed

Description

78%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 clearly answers both what and when with concrete, natural trigger phrases and a distinct worktree niche. It is slightly held back by a broad trigger tail that invites overlap and by only naming a couple of concrete actions.

Suggestions

Trim the trailing trigger list ('lifecycle, debugging, implementation, review, or multi-agent workflows') to the core worktree lifecycle verbs to reduce overlap with debugging/review skills.

Add one or two more concrete actions (e.g., 'create, resume, and switch isolated feature worktrees') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (worktree) and two concrete actions ('setup and resume guidance') but does not enumerate the broader set of concrete operations, matching the '1-2 concrete actions but not comprehensive' anchor rather than the several-action level 4.	3 / 5
Completeness	Explicitly states what it does ('Worktree setup and resume guidance for isolated feature work') and when to use it with concrete trigger phrases, satisfying the level-5 anchor for both what and when.	5 / 5
Trigger Term Quality	'Use when starting, resuming, switching, or verifying a feature branch/worktree' gives good natural-phrase coverage users would say, but stops short of the comprehensive synonyms/extensions level 5 requires.	4 / 5
Distinctiveness Conflict Risk	The worktree niche is clear and distinct, but the broad trigger tail ('for lifecycle, debugging, implementation, review, or multi-agent workflows') raises minor overlap risk with debugging/review skills, keeping it just below level 5.	4 / 5
	Total	16 / 20 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: codeaholicguy/ai-devkit
Path: skills/dev-worktree/SKILL.md
Commit: d56e554

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