worktrees

Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.

Quality

64%

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

Quality

Content

75%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 a well-structured, actionable orchestration protocol with strong safety guards and a clear four-phase workflow. It is concise and assumes Claude's competence, with only minor gaps in explicit error-recovery feedback loops and progressive file splitting.

Suggestions

Make the validation feedback loop explicit in Phase 3 (e.g., "If checks fail, fix in the lane and re-run before requesting integration").

Add one concrete worked example with real slug/branch values to make the worktree-add command copy-paste ready.

Consider moving the .slim/worktrees.json schema and ignore-file blocks into a reference file to keep SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Git competence; each section (contract, safety, phases, ignore setup) earns its place, with only minor prose (e.g., the intro value statement) that could be trimmed.	4 / 5
Actionability	Provides concrete executable commands (git worktree add/remove, ignore blocks, JSON manifest) with appropriate placeholders; lacks a fully copy-paste worked example with real values.	4 / 5
Workflow Clarity	Four clearly sequenced phases with a pre-flight checklist and explicit user-confirmation guards plus Phase 3 verification/diff checkpoints; the validate->fix->retry feedback loop is implied rather than spelled out.	4 / 5
Progressive Disclosure	Well-organized into clear headers with easy navigation and no nested references; content is appropriately inline for a single-file protocol, though the JSON schema and ignore blocks could optionally live in references.	4 / 5
	Total	16 / 20 Passed

Description

53%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 names a clear, distinct niche (Git worktrees) with a serviceable scope clause, but relies on a single generic verb and omits an explicit "Use when..." trigger with natural synonyms. It is solid but could be sharpened with concrete actions and explicit trigger phrasing.

Suggestions

Add an explicit "Use when..." clause listing concrete triggers (e.g., risky refactors, parallel branches, isolated experiments, context switching without committing).

Replace the single generic verb "Manage" with several concrete actions (create, delegate, integrate, prune worktree lanes).

Include natural synonyms users would say ("branches", "isolated environment", "spikes") alongside "worktrees".

Dimension	Reasoning	Score
Specificity	Names the domain ("Git worktrees") and one concrete action ("Manage") plus scope context ("complex, risky, or parallel work"), but does not enumerate multiple specific actions like create/merge/prune.	3 / 5
Completeness	Has a clear "what" (manage worktrees as isolated lanes) and a weak "when" ("for complex, risky, or parallel work"), but lacks an explicit "Use when..." trigger clause, capping completeness at 3.	3 / 5
Trigger Term Quality	"Git worktrees" and "parallel work" are relevant natural keywords, but common synonyms like "branches", "isolation", or "experiments" are missing.	3 / 5
Distinctiveness Conflict Risk	"Git worktrees" is a clear, distinct niche with minimal conflict risk; trigger phrasing is slightly less explicit than the anchor's "Use when" form.	4 / 5
	Total	13 / 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: alvinunreal/oh-my-opencode-slim
Path: src/skills/worktrees/SKILL.md
Commit: 3222930

Reviewed: 1 day 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.