Worktree-first development environment — create per-issue or per-PR git worktrees, optionally with tmux sessions, so multiple work streams don't collide.
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 19 of 20 test cases with the skill, and 9 of 20 without it.
Without skill45%
With skill95%
Checks it passed that the model alone missed
The created branch is named issue/551-add-oauth
The git worktree add command targets ../payments-pr-104
The created branch uses the name experiment/vulkan-renderer
and 14 more in the full report
11 fixed10 passed either way1 still failing0 broke
Pass-rate lift
+50 pp
Tokens
-10%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 8/19/2026v121 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
I need to set up an experiment worktree named 'vector-search' for the 'search-engine' repository. What branch name convention should be used when creating this experiment branch?
What was checked, without and with the skill
Checked
Without skill
With skill
The command specifies a branch name starting with the experiment/ prefix
Missed
Passed
case-17 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md67 linessingle file
Dev Project Session Manager
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Worktree-first development. Create per-issue or per-PR git worktrees so multiple work streams (different bugs, different features) don't collide on the same checkout.
Use When
Working on 2+ parallel branches that touch the same files
Switching contexts often (review a PR while your own work is in progress)
Long-running experiments that you don't want to disturb your main checkout
Do Not Use When
Single feature, single branch
Project doesn't use git
Disk space is tight (worktrees duplicate the working tree)
Workflow
Create
# Per issue
git worktree add ../{repo}-issue-123 -b issue/123-fix-auth
# Per PR (review)
git worktree add ../{repo}-pr-456 origin/feature/foo
# Per experiment
git worktree add ../{repo}-experiment-perf -b experiment/perf