Catalog
Yeachan-Heo/project-session-manager

Yeachan-Heo

project-session-manager

Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions

NewUpdated Sep 11, 2026

Project Session Manager (PSM) Skill

psm is the compatibility alias for this canonical skill entrypoint.

Quick Start (worktree-first): Start with omc teleport when you want an isolated issue/PR/feature worktree before adding any tmux/session orchestration:

omc teleport #123          # Create worktree for issue/PR
omc teleport my-feature    # Create worktree for feature
omc teleport list          # List worktrees

See Teleport Command below for details.

Automate isolated development environments using git worktrees and tmux sessions with Claude Code. Enables parallel work across multiple tasks, projects, and repositories.

Canonical slash command: /oh-my-claudecode:project-session-manager (alias: /oh-my-claudecode:psm).

Commands

Command Description Example
review <ref> PR review session /psm review omc#123
fix <ref> Issue fix session /psm fix omc#42
feature <proj> <name> Feature development /psm feature omc add-webhooks
list [project] List active sessions /psm list
attach <session> Attach to session /psm attach omc:pr-123
kill <session> Kill session /psm kill omc:pr-123
cleanup Clean merged/closed /psm cleanup
status Current session info /psm status

Project References

Supported formats:

  • Alias: omc#123 (requires ~/.psm/projects.json)
  • Full: owner/repo#123
  • URL: https://github.com/owner/repo/pull/123
  • Current: #123 (uses current directory's repo)

Configuration

Project Aliases (~/.psm/projects.json)

{
  "aliases": {
    "omc": {
      "repo": "Yeachan-Heo/oh-my-claudecode",
      "local": "~/Workspace/oh-my-claudecode",
      "default_base": "main"
    }
  },
  "defaults": {
    "worktree_root": "~/.psm/worktrees",
    "cleanup_after_days": 14
  }
}

Providers

PSM supports multiple issue tracking providers:

Provider CLI Required Reference Formats Commands
GitHub (default) gh owner/repo#123, alias#123, GitHub URLs review, fix, feature
Jira jira PROJ-123 (if PROJ configured), alias#123 fix, feature

Jira Configuration

To use Jira, add an alias with jira_project and provider: "jira":

{
  "aliases": {
    "mywork": {
      "jira_project": "MYPROJ",
      "repo": "mycompany/my-project",
      "local": "~/Workspace/my-project",
      "default_base": "develop",
      "provider": "jira"
    }
  }
}

Important: The repo field is still required for cloning the git repository. Jira tracks issues, but you work in a git repo.

For non-GitHub repos, use clone_url instead:

{
  "aliases": {
    "private": {
      "jira_project": "PRIV",
      "clone_url": "git@gitlab.internal:team/repo.git",
      "local": "~/Workspace/repo",
      "provider": "jira"
    }
  }
}

Jira Reference Detection

PSM only recognizes PROJ-123 format as Jira when PROJ is explicitly configured as a jira_project in your aliases. This prevents false positives from branch names like FIX-123.

Jira Examples

# Fix a Jira issue (MYPROJ must be configured)
psm fix MYPROJ-123

# Fix using alias (recommended)
psm fix mywork#123

# Feature development (works same as GitHub)
psm feature mywork add-webhooks

# Note: 'psm review' is not supported for Jira (no PR concept)
# Use 'psm fix' for Jira issues

Jira CLI Setup

Install the Jira CLI:

# macOS
brew install ankitpokhrel/jira-cli/jira-cli

# Linux
# See: https://github.com/ankitpokhrel/jira-cli#installation

# Configure (interactive)
jira init

The Jira CLI handles authentication separately from PSM.

Directory Structure

~/.psm/
├── projects.json       # Project aliases
├── sessions.json       # Active session registry
└── worktrees/          # Worktree storage
    └── <project>/
        └── <type>-<id>/

Session Naming

The public session ID (colon form, e.g. omc:pr-123) is the human-facing identifier stored in sessions.json and used with psm attach/psm kill. tmux reserves : and . for its session:window.pane target syntax and silently rewrites them, so the actual tmux session name uses a tmux-safe form where those characters become _ (issue #3528). PSM translates the public ID to the tmux-safe name at every tmux boundary; attach directly with the tmux-safe name.

Type Public ID (psm attach/kill) Tmux Session (tmux attach -t) Worktree Dir
PR Review omc:pr-123 psm_omc_pr-123 ~/.psm/worktrees/omc/pr-123
Issue Fix omc:issue-42 psm_omc_issue-42 ~/.psm/worktrees/omc/issue-42
Feature omc:feat-auth psm_omc_feat-auth ~/.psm/worktrees/omc/feat-auth

Implementation Protocol

When the user invokes a PSM command, follow this protocol:

Parse Arguments

Parse {{ARGUMENTS}} to determine:

  1. Subcommand: review, fix, feature, list, attach, kill, cleanup, status
  2. Reference: project#number, URL, or session ID
  3. Options: --branch, --base, --no-claude, --no-tmux, etc.

Subcommand: review <ref>

Purpose: Create PR review session

Steps:

  1. Resolve reference:

    # Read project aliases
    cat ~/.psm/projects.json 2>/dev/null || echo '{"aliases":{}}'
    
    # Parse ref format: alias#num, owner/repo#num, or URL
    # Extract: project_alias, repo (owner/repo), pr_number, local_path
    
  2. Fetch PR info:

    gh pr view <pr_number> --repo <repo> --json number,title,author,headRefName,baseRefName,body,files,url
    
  3. Ensure local repo exists:

    # If local path doesn't exist, clone
    if [[ ! -d "$local_path" ]]; then
      git clone "https://github.com/$repo.git" "$local_path"
    fi
    
  4. Create worktree:

    worktree_path="$HOME/.psm/worktrees/$project_alias/pr-$pr_number"
    
    # Fetch PR branch
    cd "$local_path"
    git fetch origin "pull/$pr_number/head:pr-$pr_number-review"
    
    # Create worktree
    git worktree add "$worktree_path" "pr-$pr_number-review"
    
  5. Create session metadata:

    cat > "$worktree_path/.psm-session.json" << EOF
    {
      "id": "$project_alias:pr-$pr_number",
      "type": "review",
      "project": "$project_alias",
      "ref": "pr-$pr_number",
      "branch": "<head_branch>",
      "base": "<base_branch>",
      "created_at": "$(date -Iseconds)",
      "tmux_session": "psm_${project_alias}_pr-$pr_number",
      "worktree_path": "$worktree_path",
      "source_repo": "$local_path",
      "github": {
        "pr_number": $pr_number,
        "pr_title": "<title>",
        "pr_author": "<author>",
        "pr_url": "<url>"
      },
      "state": "active"
    }
    EOF
    
  6. Update sessions registry:

    # Add to ~/.psm/sessions.json
    
  7. Create tmux session (tmux-safe name; :/. are translated to _):

    tmux new-session -d -s "psm_${project_alias}_pr-$pr_number" -c "$worktree_path"
    
  8. Launch Claude Code (unless --no-claude):

    # --dangerously-skip-permissions prevents the "Do you trust this directory?" prompt
    # and repeated tool-approval prompts from stalling the session (issue #2508).
    tmux send-keys -t "psm_${project_alias}_pr-$pr_number" "claude --dangerously-skip-permissions" Enter
    
    # After claude boots (PSM_CLAUDE_STARTUP_DELAY, default 5s), deliver the task.
    # Use -l (literal) so special characters are not misinterpreted by tmux.
    sleep "${PSM_CLAUDE_STARTUP_DELAY:-5}"
    tmux send-keys -t "psm_${project_alias}_pr-$pr_number" -l \
      "Review PR #$pr_number: \"$pr_title\" by @$pr_author ($head_branch → $base_branch). URL: $pr_url." Enter
    
  9. Output session info:

    Session ready!
    
      ID: omc:pr-123
      Worktree: ~/.psm/worktrees/omc/pr-123
      Tmux: psm_omc_pr-123
    
    To attach: tmux attach -t psm_omc_pr-123   (or: psm attach omc:pr-123)
    

Subcommand: fix <ref>

Purpose: Create issue fix session

Steps:

  1. Resolve reference (same as review)

  2. Fetch issue info:

    gh issue view <issue_number> --repo <repo> --json number,title,body,labels,url
    
  3. Create feature branch:

    cd "$local_path"
    git fetch origin main
    branch_name="fix/$issue_number-$(echo "$title" | tr ' ' '-' | tr '[:upper:]' '[:lower:]' | head -c 30)"
    git checkout -b "$branch_name" origin/main
    
  4. Create worktree:

    worktree_path="$HOME/.psm/worktrees/$project_alias/issue-$issue_number"
    git worktree add "$worktree_path" "$branch_name"
    
  5. Create session metadata (similar to review, type="fix")

  6. Update registry, create tmux, launch claude: Same as review, but pass issue context as the initial task prompt:

    tmux send-keys -t "psm_${project_alias}_issue-$issue_number" "claude --dangerously-skip-permissions" Enter
    # After claude boots, deliver the task (see PSM_CLAUDE_STARTUP_DELAY):
    tmux send-keys -t "psm_${project_alias}_issue-$issue_number" -l \
      "Fix issue #$issue_number: \"$issue_title\". URL: $issue_url. Branch: $branch_name." Enter
    

Subcommand: feature <project> <name>

Purpose: Start feature development

Steps:

  1. Resolve project (from alias or path)

  2. Create feature branch:

    cd "$local_path"
    git fetch origin main
    branch_name="feature/$feature_name"
    git checkout -b "$branch_name" origin/main
    
  3. Create worktree:

    worktree_path="$HOME/.psm/worktrees/$project_alias/feat-$feature_name"
    git worktree add "$worktree_path" "$branch_name"
    
  4. Create session, tmux, launch claude with feature context as initial prompt:

    tmux send-keys -t "psm_${project_alias}_feat-$feature_name" "claude --dangerously-skip-permissions" Enter
    tmux send-keys -t "psm_${project_alias}_feat-$feature_name" -l \
      "Implement feature \"$feature_name\" for project $project. Branch: $branch_name." Enter
    

Subcommand: list [project]

Purpose: List active sessions

Steps:

  1. Read sessions registry:

    cat ~/.psm/sessions.json 2>/dev/null || echo '{"sessions":{}}'
    
  2. Check tmux sessions:

    tmux list-sessions -F "#{session_name}" 2>/dev/null | grep "^psm_"
    
  3. Check worktrees:

    ls -la ~/.psm/worktrees/*/ 2>/dev/null
    
  4. Format output:

    Active PSM Sessions:
    
    ID                 | Type    | Status   | Worktree
    -------------------|---------|----------|---------------------------
    omc:pr-123        | review  | active   | ~/.psm/worktrees/omc/pr-123
    omc:issue-42      | fix     | detached | ~/.psm/worktrees/omc/issue-42
    

Subcommand: attach <session>

Purpose: Attach to existing session

Steps:

  1. Parse session ID: project:type-number

  2. Verify session exists:

    tmux has-session -t "psm_${session_id//[.:]/_}" 2>/dev/null   # translate public id to tmux-safe name
    
  3. Attach:

    tmux attach -t "psm_${session_id//[.:]/_}"
    

Subcommand: kill <session>

Purpose: Kill session and cleanup

Steps:

  1. Kill tmux session:

    tmux kill-session -t "psm_${session_id//[.:]/_}" 2>/dev/null
    
  2. Remove worktree:

    worktree_path=$(jq -r ".sessions[\"$session_id\"].worktree" ~/.psm/sessions.json)
    source_repo=$(jq -r ".sessions[\"$session_id\"].source_repo" ~/.psm/sessions.json)
    
    cd "$source_repo"
    git worktree remove "$worktree_path" --force
    
  3. Update registry:

    # Remove from sessions.json
    

Subcommand: cleanup

Purpose: Clean up merged PRs and closed issues

Steps:

  1. Read all sessions

  2. For each PR session, check if merged:

    gh pr view <pr_number> --repo <repo> --json merged,state
    
  3. For each issue session, check if closed:

    gh issue view <issue_number> --repo <repo> --json closed,state
    
  4. Clean up merged/closed sessions:

    • Kill tmux session
    • Remove worktree
    • Update registry
  5. Report:

    Cleanup complete:
      Removed: omc:pr-123 (merged)
      Removed: omc:issue-42 (closed)
      Kept: omc:feat-auth (active)
    

Subcommand: status

Purpose: Show current session info

Steps:

  1. Detect current session from tmux or cwd:

    tmux display-message -p "#{session_name}" 2>/dev/null
    # or check if cwd is inside a worktree
    
  2. Read session metadata:

    cat .psm-session.json 2>/dev/null
    
  3. Show status:

    Current Session: omc:pr-123
    Type: review
    PR: #123 - Add webhook support
    Branch: feature/webhooks
    Created: 2 hours ago
    

Error Handling

Error Resolution
Worktree exists Offer: attach, recreate, or abort
PR not found Verify URL/number, check permissions
No tmux Warn and skip session creation
No gh CLI Error with install instructions

Teleport Command

The omc teleport command provides a lightweight alternative to full PSM sessions. It creates git worktrees without tmux session management — ideal for quick, isolated development.

Usage

# Create worktree for an issue or PR
omc teleport #123
omc teleport owner/repo#123
omc teleport https://github.com/owner/repo/issues/42

# Create worktree for a feature
omc teleport my-feature

# List existing worktrees
omc teleport list

# Remove a worktree
omc teleport remove issue/my-repo-123
omc teleport remove --force feat/my-repo-my-feature

Options

Flag Description Default
--worktree Create worktree (default, kept for compatibility) true
--path <path> Custom worktree root directory ~/Workspace/omc-worktrees/
--base <branch> Base branch to create from main
--json Output as JSON false

Worktree Layout

~/Workspace/omc-worktrees/
├── issue/
│   └── my-repo-123/        # Issue worktrees
├── pr/
│   └── my-repo-456/        # PR review worktrees
└── feat/
    └── my-repo-my-feature/ # Feature worktrees

PSM vs Teleport

Feature PSM Teleport
Git worktree Yes Yes
Tmux session Yes No
Claude Code launch Yes No
Session registry Yes No
Auto-cleanup Yes No
Project aliases Yes No (uses current repo)

Use PSM for full managed sessions. Use teleport for quick worktree creation.


Requirements

Required:

  • git - Version control (with worktree support v2.5+)
  • jq - JSON parsing
  • tmux - Session management (optional, but recommended)

Optional (per provider):

  • gh - GitHub CLI (for GitHub workflows)
  • jira - Jira CLI (for Jira workflows)

Initialization

On first run, create default config:

mkdir -p ~/.psm/worktrees ~/.psm/logs

# Create default projects.json if not exists
if [[ ! -f ~/.psm/projects.json ]]; then
  cat > ~/.psm/projects.json << 'EOF'
{
  "aliases": {
    "omc": {
      "repo": "Yeachan-Heo/oh-my-claudecode",
      "local": "~/Workspace/oh-my-claudecode",
      "default_base": "main"
    }
  },
  "defaults": {
    "worktree_root": "~/.psm/worktrees",
    "cleanup_after_days": 14,
    "auto_cleanup_merged": true
  }
}
EOF
fi

# Create sessions.json if not exists
if [[ ! -f ~/.psm/sessions.json ]]; then
  echo '{"version":1,"sessions":{},"stats":{"total_created":0,"total_cleaned":0}}' > ~/.psm/sessions.json
fi
Files20
20 files · 92.1 KB

Select a file to preview

Overall Score

78/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

76

Quality

82

Clarity

78

Completeness

74

Summary

PSM (Project Session Manager) is a worktree-first dev environment manager that automates isolated development using git worktrees and tmux sessions across multiple issue tracking providers (GitHub, Jira, GitLab, Bitbucket). It creates scoped sessions for PR reviews, issue fixes, and feature development, with integrated Claude Code launching and session lifecycle management.

Static Analysis Findings

2 findings

Patterns detected by deterministic static analysis before AI scoring. Hover over any finding code for detailed information and remediation guidance.

Destructive Operation
SEC-001Recursive Deletion2x in 2 filesMax: B

Recursive deletion pattern (rm -rf)

tests/test-psm-prompt-injection.shrm -rf
lib/worktree.shrm -rf
SEC-002Privilege Escalation

Privilege escalation (sudo)

psm.shsudo a

Detected Capabilities

file writedirectory creationshell execution (git, tmux, gh, jira CLIs)json parsing and modificationprocess management (tmux)git operations (clone, fetch, branch, worktree)external CLI calls (gh, jira, glab, az)file locking for atomic operationstemplate rendering

Trigger Keywords

Phrases that agents use to match this skill to user intent.

create pr review sessionisolated issue worktreemanage dev environmentsparallel issue fixingtmux session orchestrationgithub jira integration

Risk Signals

WARNING

Recursive deletion (rm -rf) in worktree cleanup path

lib/worktree.sh:psm_remove_worktree
WARNING

Recursive deletion (rm -rf) in fallback cleanup after git worktree remove fails

lib/worktree.sh:psm_remove_worktree
INFO

Sudo privilege escalation pattern detected

psm.sh:check_dependencies
INFO

External CLI dependency execution (gh, jira, glab, az, curl)

lib/providers/*.sh, psm.sh
WARNING

Environment variable access for provider tokens (BITBUCKET_TOKEN, BITBUCKET_USERNAME, BITBUCKET_APP_PASSWORD, GITEA_URL, GITEA_TOKEN)

lib/providers/bitbucket.sh, lib/providers/gitea.sh
INFO

Curl-based API calls to external services (Bitbucket, Gitea)

lib/providers/bitbucket.sh, lib/providers/gitea.sh

Referenced Domains

External domains referenced in skill content, detected by static analysis.

...api.bitbucket.orgbitbucketbitbucket.orgdevgitea.com}githubgithub.comgitlabgitlab.com

Use Cases

  • Start isolated PR review sessions with full context
  • Create feature branches in dedicated worktrees with tmux
  • Fix GitHub issues in parallel development environments
  • Manage Jira issues with git-based workflows
  • Auto-cleanup merged PRs and closed issues
  • Attach/detach from tmux development sessions
  • Multi-project session orchestration with project aliases

Quality Notes

  • Well-documented command reference and configuration schema with examples
  • Comprehensive error handling with fallbacks (e.g., no-tmux mode, local repo fallback)
  • Clear separation of concerns across library modules (config, parse, worktree, tmux, session, providers)
  • Strong validation of user input (reference parsing, path validation, worktree path checks)
  • Extensive test coverage for prompt injection and Jira provider edge cases
  • Good use of atomicity (file locking) for session registry updates
  • Provider interface is extensible and well-abstracted
  • Session naming strategy handles tmux character restrictions correctly (issue #3528)
  • Template rendering with validation prevents prompt injection
  • Comprehensive inline comments explaining complex logic (especially worktree cleanup and session naming)
  • Missing: explicit documentation of security boundaries for environment variable usage
Model: claude-haiku-4-5-20251001Analyzed: Sep 11, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v1.2

    Content updated

    ✦ AITmux session names now use underscore-safe format (colons and dots become underscores); public session IDs (colon form) remain unchanged but are translated at tmux boundaries. Adds test file for…

    2026-09-11

    LATEST
  2. v1.1

    Content updated

    ✦ AIAdds claude --dangerously-skip-permissions flag and task-delivery prompts for review, issue, and feature sessions.

    2026-04-20

    View This Version
  3. v1.0

    2026-04-12

    View This VersionInitial version

Use Yeachan-Heo/project-session-manager in your dev environment

Command Palette

Search for a command to run...