Skip to content
Back to skills

Dev Project Session Manager

ASecurity

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

  • 529 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 29, 2026
ai-agentsbashgit

Security analysis

A100/100

Scanned May 29, 2026

npx -y skills add evolution-foundation/evo-nexus --skill dev-project-session-manager --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dev Project Session Manager?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dev Project Session Manager
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/evolution-foundation-dev-project-session-manager/badge)](https://www.skillsdirectory.com/skills/evolution-foundation-dev-project-session-manager)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
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
```bash
# 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
```bash
tmux new-session -d -s {repo}-issue-123 -c ../{repo}-issue-123
```

### List
```bash
git worktree list
```

### Remove
```bash
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`:

```markdown
## 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…