dev-project-session-manager

Create, list, and remove isolated git worktrees with optional tmux sessions.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-project-session-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-project-session-manager
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-project-session-manager
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-project-session-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multiple parallel streams of development can collide in a single checkout, causing lost work, confusing contexts, and disrupted reviews; this Skill provides a worktree-first approach to keep each task isolated and reproducible.

Core Features & Use Cases

  • Create per-issue, per-PR, or per-experiment git worktrees so separate branches do not interfere with one another.
  • Optionally start a tmux session per worktree to maintain terminal state and workflows tied to each working tree.
  • Manage lifecycle operations: list active worktrees, remove completed worktrees, and save a documented map of active worktrees for team visibility and handoffs.
  • Use Case: Review a contributor's PR in one worktree while continuing feature development in another without switching branches or stashing changes.

Quick Start

Create a new per-issue git worktree and an optional tmux session for issue 123 so you can work in isolation without affecting your main branch.

Frequently Asked Questions about dev-project-session-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use git worktrees for parallel development without branch collisions?

Git worktrees create isolated working trees for separate branches, preventing workspace collisions during parallel development. This Skill automates creating per-issue or per-PR worktrees so multiple branches do not interfere with one another.

Can I review a contributor's PR while continuing feature development in the same git repository?

Reviewing a PR while developing features requires isolated git worktrees. This Skill creates separate working trees for each task, allowing you to review contributions without switching branches or stashing your uncommitted local changes.

How do I start a tmux session tied to a specific git worktree?

Starting a tmux session per worktree maintains terminal state tied to each working tree. This Skill optionally creates a tmux session during worktree setup, ensuring terminal workflows remain isolated alongside your parallel development branches.

What is the best way to manage and document active git worktrees for team handoffs?

Managing active worktrees involves listing, removing, and documenting isolated working trees. This Skill manages the full lifecycle of git worktrees and produces a documented map of active trees to provide team visibility and facilitate project handoffs.

When should I use git worktrees instead of stashing changes or cloning repositories?

Git worktrees are ideal for long-running experiments, multiple branch workflows, and PR reviews requiring separate working trees. Use this approach when stashing changes becomes unmanageable or context-switching disrupts your development and review processes.