playbooks

home / skills / yeachan-heo / oh-my-claudecode / psm

psm skill

/skills/psm

This skill helps you manage isolated dev environments with git worktrees and tmux by delegating to the project session manager.

npx playbooks add skill yeachan-heo/oh-my-claudecode --skill psm

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
561 B
---
name: psm
description: Project Session Manager - isolated dev environments with git worktrees and tmux
---

# PSM (Project Session Manager Alias)

PSM is a shorthand alias for `/oh-my-claudecode:project-session-manager`.

## Usage

```
/oh-my-claudecode:psm <arguments>
```

## Behavior

This skill is identical to `/oh-my-claudecode:project-session-manager`. Invoke the Project Session Manager skill with the same arguments.

Follow the Project Session Manager skill's full documentation for worktree management, tmux session handling, and template usage.

Overview

This skill provides a shorthand alias for invoking the Project Session Manager (PSM) used to create isolated development environments with git worktrees and tmux. It forwards arguments to the full Project Session Manager command so teams can quickly open, switch, and manage session contexts. The alias preserves the same behavior and options as the canonical skill for consistency across workflows.

How this skill works

When called, the alias forwards all arguments to the underlying Project Session Manager implementation. The manager creates or attaches tmux sessions, sets up git worktrees for isolated feature branches, and applies optional templates for environment bootstrapping. All worktree and tmux lifecycle operations follow the Project Session Manager's rules and configuration.

When to use it

  • Start an isolated development session for a new feature or bugfix
  • Switch between parallel work contexts without affecting the main branch
  • Onboard collaborators to a shared workspace with consistent tmux layouts
  • Run multi-agent orchestration tasks that require separated codebases
  • Automate session creation in CI or developer tooling scripts

Best practices

  • Use descriptive session and worktree names to avoid collisions
  • Commit or stash local changes before creating a worktree to prevent data loss
  • Keep templates small and reproducible for fast environment setup
  • Share a common configuration file with your team to standardize sessions
  • Regularly prune unused worktrees and tmux sessions to reduce clutter

Example use cases

  • Create a new worktree and tmux session for a hotfix with one command
  • Open multiple isolated sessions to run parallel experiments safely
  • Provision per-task environments for a multi-agent Claude Code workflow
  • Automate developer environment creation in onboarding scripts
  • Quickly recover and reattach to a previously started session after reconnecting

FAQ

Is this alias different from the main Project Session Manager?

No. The alias simply forwards arguments and behaves identically to the main Project Session Manager.

Do I need special permissions to use it?

You need git and tmux installed and normal filesystem permissions for the repository and worktree locations.

Will using worktrees affect my main branch?

Worktrees provide isolated checkouts; they do not modify the main branch unless you explicitly merge or push changes.