project-session-manager

Creates isolated git worktrees and optional tmux sessions for PR reviews, issues, and features.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/nichobbs/lyric-lang --skill project-session-manager-nichobbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-session-manager
Source: https://github.com/nichobbs/lyric-lang/tree/main/.claude/skills/project-session-manager
Command: npx skills add https://github.com/nichobbs/lyric-lang --skill project-session-manager-nichobbs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Project Session Manager (PSM) reduces context switching by automatically creating isolated git worktrees and (optionally) tmux sessions for PR reviews, issue fixes, and feature development, so you can focus on one change at a time.

Core Features & Use Cases

  • Worktree-first isolation for PRs, issues, and features using git worktrees
  • Session orchestration with tmux to run Claude Code in an associated terminal session
  • Provider-backed context gathering using GitHub CLI (gh) for PR/issue details and Jira CLI (jira) for Jira issues
  • Works with project aliases via a configurable projects.json for consistent repo cloning and defaults

Quick Start

Create an isolated PR review session for omc#123 by running: omc 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 create isolated git worktrees for reviewing pull requests?

You can create isolated git worktrees for PR reviews by parsing GitHub URLs or references like alias#number to fetch metadata and automatically generate reproducible local branches. This allows you to focus on one change at a time without context switching.

Can I launch tmux sessions alongside git worktrees for feature development?

Yes, you can optionally orchestrate tmux sessions alongside git worktrees. This launches an associated terminal session to run Claude Code with rendered task context safely and deterministically for your feature development workflow.

Do I need the GitHub CLI and Jira CLI to fetch issue metadata for worktrees?

Yes, you need the gh CLI for GitHub PR and issue details, and the jira CLI for Jira issue keys. These provider CLIs fetch the required metadata to create worktrees and render the necessary task context.

What is the best way to manage parallel development environments across projects?

The best way to manage parallel environments is using project aliases configured in a projects.json file. This ensures consistent repo cloning and applies defaults when spinning up isolated worktrees driven by references like alias#number or Jira keys.

Does this approach work with Jira keys to fix issues in isolated branches?

Yes, it works with Jira keys to fix issues by parsing the reference to determine the provider and local paths. It fetches metadata using the Jira CLI and creates an isolated worktree to safely develop the fix.

What are the limitations of using git worktrees for isolated task sessions?

Limitations include dependencies on git, jq, tmux, gh, and jira CLIs being installed. It requires a root SKILL entry and configured project aliases to correctly parse references and safely launch Claude Code deterministically.