Skip to content
Automation
Skill

/dev-project-session-manager

Worktree-first development environment — create per-issue or per-PR git worktrees, optionally with tmux sessions, so multiple work streams don't collide.

From plugin
evo-nexus
520193 skills38 agents40 commands9 MCP
Install
$ npx -y skills add evolution-foundation/evo-nexus --skill dev-project-session-manager --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/dev-project-session-manager

Context preview

The summary Claude sees to decide when to auto-load this skill.

Worktree-first development environment — create per-issue or per-PR git worktrees, optionally with tmux sessions, so multiple work streams don't collide.

SKILL.md

dev-project-session-manager.SKILL.md
name: dev-project-session-manager
description: Worktree-first development environment — create per-issue or per-PR git worktrees, optionally with tmux sessions, so multiple work streams don't collide.

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

Optional: tmux session per worktree

tmux new-session -d -s {repo}-issue-123 -c ../{repo}-issue-123

List

git worktree list

Remove

git worktree remove ../{repo}-issue-123
git branch -d issue/123-fix-auth  # if merged

Naming Convention

  • `{repo}-issue-{N}` — issue work
  • `{repo}-pr-{N}` — PR review
  • `{repo}-experiment-{name}` — experiments
  • `{repo}-hotfix-{name}` — urgent fixes

Output

Save the active worktree map to `workspace/development/research/[C]worktrees-{date}.md`:

## Active Worktrees — {date}

| Path | Branch | Purpose | tmux session |
|---|---|---|---|
| ../evo-ai-issue-123 | issue/123 | fix auth bug | evo-ai-issue-123 |
| ../evo-ai-pr-456 | origin/feat/x | review | (none) |

Pairs With

  • `@flow-git` (when worktrees need rebasing or commit splitting)
  • Any agent that needs to work in isolation
Read more
Ships withevo-nexus

The open source operating system for AI-powered businesses

Get the whole plugin

Other skills on evo-nexus.