Menu
Open a tmux window with a Claude Code session for a GitHub issue or PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Check remote server CPU, memory, and GPU availability via SSH
Cold-start into a worktree/clone from a fresh conversation — read the PR, issue, and any status files, figure out where things stand, then STOP and ask the user what to do next. Use for a fresh conversation dropped into a bip-spawn or bip-epic-spawn worktree/clone that already has history (a PR, an in-progress phase, or a stalled worker).
Quick poll of tracked EPICs and code repos for new manuscript-relevant results
Persist manuscript session state before context reset
Cold-start for a manuscript session — the paper is the source of truth and shared context; discuss results, orchestrate research through issues/PRs, and update the paper as threads complete
Spawn a Claude session in a clone for an EPIC issue
| name | bip-spawn |
| description | Open a tmux window with a Claude Code session for a GitHub issue or PR. |
Open a tmux window for GitHub issue or PR review.
Just run bip spawn directly. Do not attempt to construct claude or tmux commands yourself — bip spawn handles all of that.
bip spawn org/repo#123
bip spawn https://github.com/org/repo/pull/42
bip spawn org/repo#123 --prompt "Rebase and fix conflicts"
repo#123There are two distinct ways to use bip spawn. Pick deliberately:
--prompt): opens a Claude session with the
issue or PR context loaded and waits at an empty prompt. Use this
when you will drive the next steps in the spawned window.--prompt "/bip-issue-work <N>" (for
issues) or --prompt "/bip-pr-review" (for PRs). The spawned Claude
starts the workflow autonomously — the right choice when the parent
session is delegating implementation and won't be steering.Example handoff:
bip spawn matsengrp/phyz#1453 --prompt "/bip-issue-work 1453"
If you're spawning from inside a /bip-pr-land or similar handoff
context, the handoff form is almost always what you want.
--prompt "..." — Custom prompt instead of default review promptBy default, bip spawn opens its tmux window in the canonical clone of
the repo — every spawn shares one working tree. To get one linked git
worktree per issue instead (so concurrent spawns don't share a branch
checkout), add a layout: block to ~/.config/bip/config.yml:
layout:
mode: worktree
worktree:
root: "~/re/{repo}-workers" # {repo} = matsen/bipartite -> "bipartite"
slot: "issue-{issue}" # supports {issue}, {pr}, {branch}, {slug}
Per-repo overrides live in sources.yml (see docs/guides/layout.md).
With no layout: block, behavior is identical to before issue #149.
When worktree mode fires, bip spawn runs git worktree add from the
canonical clone on a fresh branch named <N>-<slug>, and the spawned
tmux window opens in the new worktree. bip pr-land later detects the
worktree, lands the PR from the primary clone, and removes the worktree.