parallel-worktrees
Set up parallel coding sessions using git worktrees for zero dead time. Use when blocked on tests, builds, or wanting to explore multiple approaches simultaneously.
Install with Tessl CLI
npx tessl i github:rohitg00/pro-workflow --skill parallel-worktrees86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 description has good structure with explicit 'Use when' guidance and a clear, distinctive niche around git worktrees. However, it could benefit from more specific concrete actions beyond 'set up' and additional natural trigger terms that users might actually say when needing this capability.
Suggestions
Add more concrete actions like 'create worktrees, manage parallel branches, clean up completed worktrees' to improve specificity
Include additional natural trigger terms users might say: 'work on multiple branches', 'context switching', 'concurrent development', 'work on two features at once'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git worktrees, parallel coding sessions) and mentions a specific action (set up), but lacks comprehensive concrete actions like 'create worktrees', 'manage branches', or 'switch between sessions'. | 2 / 3 |
Completeness | Clearly answers both what ('Set up parallel coding sessions using git worktrees for zero dead time') and when ('Use when blocked on tests, builds, or wanting to explore multiple approaches simultaneously') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms ('git worktrees', 'parallel coding', 'blocked on tests, builds') but misses common variations users might say like 'multiple branches', 'concurrent development', 'work on two things at once', or 'context switching'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focusing specifically on git worktrees for parallel development - distinct from general git skills, branching skills, or other workflow tools. The 'blocked on tests/builds' trigger is specific and unlikely to conflict. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that efficiently teaches parallel worktree usage with concrete, executable commands. The content respects Claude's intelligence and provides clear usage patterns. Minor weakness is the lack of explicit validation steps before worktree cleanup to prevent accidental work loss.
Suggestions
Add a validation checkpoint before worktree removal: 'Verify changes are committed/pushed before cleanup: `git -C ../project-feat status`'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, assuming Claude knows git basics. No unnecessary explanations of what worktrees are conceptually—jumps straight to actionable commands and patterns. | 3 / 3 |
Actionability | Provides fully executable commands throughout, from quick start to cleanup. Commands are copy-paste ready with clear examples for both Claude Code and Cursor workflows. | 3 / 3 |
Workflow Clarity | Steps are listed but validation is implicit. The workflow section mentions 'clean up the worktree' but doesn't emphasize verification that work was committed/pushed before removal, which could lead to lost work. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from quick start to detailed commands to usage patterns. Content is appropriately sized for a single file with no need for external references. | 3 / 3 |
Total | 11 / 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.
- 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.