project-session-manager

Create isolated git worktrees with tmux sessions for PR reviews.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill project-session-manager-dropsyoon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-session-manager
Source: https://github.com/dropsyoon/oh-my-claudecode/tree/main/skills/project-session-manager
Command: npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill project-session-manager-dropsyoon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, tmux, gh, jira.

What problem does it solve?

This Skill solves the problem of context switching and tangled local environments when reviewing PRs, fixing issues, or building features across multiple repositories or branches.

Core Features & Use Cases

  • Worktree-first isolated environments: Creates git worktrees per PR review, issue fix, or feature branch so each task stays clean and independent.
  • Optional tmux session orchestration: Spins up dedicated tmux sessions for each worktree to keep terminal workflows organized.
  • Provider-aware task context: Fetches PR/issue metadata from GitHub (via gh) or Jira (via jira) and injects task context for Claude Code.
  • Operational lifecycle management: Lists active sessions, attaches, kills sessions, and cleans up merged/closed tasks.
  • Use Case: You need to review multiple PRs in parallel—each one gets its own worktree and tmux-backed Claude session so you can iterate without overwriting code from other tasks.

Quick Start

Start a managed PR review by creating an isolated worktree and launching Claude in a tmux session using the command: omc psm review omc#123

Frequently Asked Questions about project-session-manager

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

FAQPage Schema
How do I isolate git worktrees for parallel PR reviews without overwriting local changes?

Isolating parallel PR reviews requires creating separate git worktrees for each task branch. This skill automates worktree creation and optional tmux session orchestration, ensuring each PR review runs in a clean, independent local environment.

Can I use Claude Code with tmux sessions to manage multiple issue fixes at the same time?

Yes, Claude Code can run inside dedicated tmux sessions to manage multiple issue fixes simultaneously. This skill orchestrates tmux sessions for each git worktree and injects fetched issue context to keep parallel terminal workflows organized.

Do I need gh and jira CLI tools installed to fetch task context for worktree automation?

Yes, you need the gh CLI installed for GitHub operations, and the jira CLI is required if fetching Jira metadata. This skill performs dependency checks for git, jq, tmux, and provider CLIs before automatically fetching and injecting task context.

What is the best way to clean up git worktrees and tmux sessions after a PR is merged?

The best way to clean up after a PR merge is using automated lifecycle management to safely remove worktrees and kill tmux sessions. This skill handles registry cleanup, automatically removing merged branches, closed tasks, and dedicated terminal sessions.

Does git worktree isolation work with Jira issue tracking or is it limited to GitHub?

Git worktree isolation works with both GitHub and Jira issue tracking. This skill is provider-aware, fetching PR and issue metadata from GitHub via gh or from Jira via its CLI, then injecting that context into the isolated worktree environment.

Why does my tmux session fail to attach when starting a worktree for an issue fix?

Tmux session attachment fails when required dependencies like tmux, git, or jq are missing, or if reference parsing fails. This skill performs dependency checks and safe session registry handling to ensure reliable creation, attachment, and cleanup of isolated environments.