hbz

Personal PR review skill. Layered walkthrough that adapts to whether this is a self-review (the user's own PR) or a colleague review. Invoke whenever the user wants to review, walk through, look at, or discuss a PR — whether they type /review-pr, share a PR number or URL, say "can you check this PR", "let's look at this before merging", "review this for me", or ask to leave comments on someone else's PR. When in doubt, invoke it.

Use when the user explicitly invokes /claude-manager. Manager-role conversations are created deliberately, normally one at a time — not auto-loaded for any meta-management session. Tracks a per-machine session registry, spawns workers in standalone tmux sessions (one tmux session per registry session), and ensures docs and journal stay complete across sessions. Manager doesn't do session work itself; it delegates implementation to spawned workers and defers to them.

Toggle the paused flag on a claude-manager session from inside the worker pane — marks the registry entry parked (or clears it) and sets a tmux switcher badge, without killing tmux or the worker. Use when a session is waiting on review or other external state and you want it easy to skip in the prefix+w switcher, or to bring a parked session back. The manager observes via its watch.

Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise reads the repo's own launch docs (README, Taskfile, Makefile, Procfile, docker-compose, bin/dev); only falls back to built-in patterns per project type if none of those describe how to launch.

Use when sending input to or reading output from a tmux pane other than the one in focus: running a command, dev server, REPL, or long-running process in a pane and waiting for it to print a prompt, port, or result; reading or scrolling pane output; or driving a shell, vim/neovim, or another agent via send-keys and capture-pane. Also when input appears to land but doesn't submit, or keystrokes get dropped.

Shut down a Claude session from inside the worker pane — captures multi-window pane snapshots and a structured resume_state file for cold resume, records resumed_session_id, kills the tmux session, and keeps the registry entry for later resumption via the manager. Worker self-serves under the registry lock; manager observes via its watch. Use when pausing work for hours or days and you want the conversation reachable again, but don't want the tmux session hanging around.

Wrap up a Claude session from inside the worker pane — captures multi-window snapshots, gathers any context worth carrying into the journal, marks the registry entry `wrap_requested`, and kills the tmux session. The manager observes via its watch and writes the journal entry per the project's schema, then removes the registry entry. Final state. Use when the work is genuinely done and you want it recorded.