agent

Orchestrate parallel PR review sub-agents using tmux sessions and git worktrees.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gakonst/dotfiles --skill agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent
Source: https://github.com/gakonst/dotfiles/tree/main/.codex/skills/agent
Command: npx skills add https://github.com/gakonst/dotfiles --skill agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill uses your Codex window as an operator console to spawn a default tmux-based control hub and per-task git worktrees, enabling parallel agent reviews and continuous monitoring without losing your main workflow.

Core Features & Use Cases

  • Control session: spawn a tmux session on the default server to host sub-agents.
  • Per-task worktrees: create isolated worktrees for independent tasks/PRs.
  • Sub-agent windows: run a separate Codex instance per task that acts as an autonomous agent.
  • Monitoring loop: operator-only intervention when a pane stalls or asks a question.

Quick Start

Quick Start: tmux new -d -s control; git worktree add .worktrees/pr-123 -b pr-123; tmux new-window -t control:pr-123 -n review; cd .worktrees/pr-123; codex --dangerously-bypass-approvals-and-sandbox

Frequently Asked Questions about agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up parallel code reviews using tmux and git worktrees?

Parallel code reviews using tmux and git worktrees involves spawning a tmux control session, creating isolated worktrees per PR, and launching dedicated agent windows for each task. This approach enables independent review workflows running simultaneously without interfering with your main development environment.

Can I run multiple PR reviews at the same time with separate agents?

Yes. The Skill orchestrates per-task sub-agents within a tmux control plane, where each PR gets its own git worktree and dedicated agent window. This setup allows parallel reviews with isolated state and passive monitoring until operator intervention is needed.

What happens when a sub-agent window stalls during a PR review?

A monitoring loop continuously flags panes that stall or require input, alerting you to intervene only when necessary. This design minimizes operator overhead by automating the review process and surfacing issues requiring human decision-making.

Do I need to manage cleanup manually after reviews complete?

The Skill implements safe, minimal intervention workflows and supports cleanup operations. After reviews finish, you can remove worktrees and tmux sessions through standard git and tmux commands without manual overhead.

How does git worktree isolation improve code review workflows?

Git worktrees create independent branch copies on disk, allowing each review task to run in isolation without branch switching or state conflicts. Combined with dedicated tmux windows, this enables simultaneous reviews of different PRs in the same repository.

What's the advantage of using a tmux control session over running reviews sequentially?

A tmux control session hosts multiple agent windows in a single namespace, enabling passive monitoring and coordination of parallel reviews. This eliminates manual switching between reviews and lets you observe all task progress from one operator console.