parallel-worktrees
Create and manage git worktrees for parallel coding sessions with zero dead time. Use when blocked on tests, builds, wanting to work on multiple branches, context switching, or exploring multiple approaches simultaneously.
88
81%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and completeness. The explicit 'Use when' clause covers multiple realistic scenarios where a user would need worktree functionality. The main weakness is that the 'what' portion could be more specific about the concrete actions beyond 'create and manage'.
Suggestions
Expand the capability list with more specific actions, e.g., 'Create, list, remove, and switch between git worktrees' instead of the vaguer 'create and manage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git worktrees) and mentions 'create and manage' as actions, but doesn't list specific concrete actions like creating worktrees, listing them, removing them, linking branches, etc. 'Manage' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (create and manage git worktrees for parallel coding sessions) and 'when' (explicit 'Use when' clause covering blocked on tests, builds, multiple branches, context switching, exploring multiple approaches). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'git worktrees', 'parallel coding', 'blocked on tests', 'builds', 'multiple branches', 'context switching', 'multiple approaches'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Git worktrees is a very specific niche that is unlikely to conflict with general git skills or other coding skills. The triggers are distinct and clearly scoped to worktree-related workflows. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, practical skill that provides actionable git worktree commands with good organization. Its main weakness is the disconnect between the abstract workflow section and the concrete commands section — integrating validation checkpoints directly into the workflow would strengthen it. The content is mostly concise but has minor redundancies across sections.
Suggestions
Integrate the concrete commands and validation steps directly into the Workflow section (e.g., step 4 should be 'Verify changes committed: `git -C ../project-feat status`, then remove: `git worktree remove ../project-feat`').
Consider merging the 'Workflow' and 'Commands' sections to eliminate redundancy and create a single clear sequence with embedded validation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary content. The 'When to Parallelize' table and 'Usage Pattern' section are somewhat redundant with the trigger section. The 'Claude Code Extras' section adds useful tool-specific info but the parenthetical '(skip if using Cursor)' is slightly verbose. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready git commands throughout. The Quick Start gives concrete commands for both Claude Code and other editors, the Commands section lists all key operations, and the guardrails include specific verification commands like `git -C ../project-feat status`. | 3 / 3 |
Workflow Clarity | The workflow section lists steps but is vague ('Create a worktree for the parallel task' and 'clean up the worktree' without specific commands inline). The guardrails section includes a verification step for checking committed changes before removal, but this isn't integrated into the workflow sequence as an explicit checkpoint. For a process involving potential data loss (removing worktrees with uncommitted changes), the validation should be more tightly coupled to the workflow steps. | 2 / 3 |
Progressive Disclosure | For a skill of this scope (single-purpose, under 100 lines, no bundle files), the content is well-organized with clear sections progressing from quick start to details to guardrails. No external references are needed and the section headers provide good navigation. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- rohitg00/pro-workflow
- Commit
9fc35f5
- Reviewed
Table of Contents
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.