project-session-manager

Manage isolated git worktrees and tmux sessions for issues and pull requests.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/INNERJOINT/HarnessSkills --skill project-session-manager-innerjoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-session-manager
Source: https://github.com/INNERJOINT/HarnessSkills/tree/main/skills/project-session-manager
Command: npx skills add https://github.com/INNERJOINT/HarnessSkills --skill project-session-manager-innerjoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need a safe, repeatable way to work on multiple issues, pull requests, and feature branches in parallel without cluttering their primary clone or branches. This Skill automates creating git worktrees, launching and attaching tmux sessions, and tracking session metadata so workspaces can be created, attached to, and cleaned up reliably.

Core Features & Use Cases

  • PR Review Sessions: Create a worktree for a pull request, start a tmux session, and launch an assistant for guided reviews.
  • Issue Fix Sessions: Spawn a branch and worktree for an issue, manage the tmux session lifecycle, and keep metadata for later cleanup.
  • Feature Worktrees: Start feature branches with isolated worktrees for long-running work without affecting other contexts.
  • Teleport Lightweight Worktrees: Quickly create and list worktrees without tmux when you only need isolation.
  • Multi-provider Support & Cleanup: Integrates with GitHub and Jira CLIs, maintains a sessions registry, and auto-cleans merged or closed sessions.

Quick Start

Run omc teleport #123 to create an isolated worktree for PR 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 manage isolated git worktrees for multiple pull requests without cluttering my main clone?

You can manage isolated git worktrees by creating separate branch directories for each pull request. This Skill automates worktree creation and tmux session orchestration, keeping parallel work isolated and preventing branch clutter in your primary repository clone.

What is the best way to automate tmux session lifecycle when switching between feature branches?

Automating tmux session lifecycle involves tracking session metadata in a registry to manage attachments and cleanup. This Skill orchestrates tmux sessions for feature branches, maintaining a registry to reliably attach, track, and clean up workspaces when branches merge.

Can I integrate Jira or GitHub CLIs to automatically spawn worktrees for issue fix sessions?

Yes, you can integrate GitHub and Jira CLIs to spawn branches and worktrees for issue fix sessions. This Skill uses gh and jira CLIs alongside jq to fetch issue context, automatically creating the corresponding isolated development environment.

Does git worktree session management support automated cleanup after branches are merged?

Git worktree session management supports automated cleanup by checking branch status and removing stale environments. This Skill maintains a session registry and auto-cleans worktrees and tmux sessions when the associated pull requests are merged or issues are closed.

When do I need a lightweight worktree without a tmux session?

You need a lightweight worktree without a tmux session when you only require directory isolation for quick tasks. This Skill provides a teleport mode to quickly create and list git worktrees without the overhead of launching and managing a tmux session.

Do I need jq installed to use this Skill for dev environment orchestration?

Yes, you need jq installed for dev environment orchestration because this Skill parses JSON output from gh and jira CLIs. It relies on jq alongside git and tmux CLIs to extract metadata for session registries and automated cleanup workflows.