What problem does it solve?
Developers increasingly work with per-feature git worktrees and need long-running development servers that survive branch switches. This Skill automates starting a development server inside a named tmux session bound to a specific worktree, enabling seamless background execution and easy log access.
Core Features & Use Cases
- Per-worktree dev servers: Launch a development server in a dedicated tmux session tied to a worktree.
- Deterministic session control: Use a configurable session ID, optional detach, and automatic cleanup after completion.
- Simple session management: List, attach to, and monitor running sessions while switching contexts across worktrees or branches.
- Use Case: Start a frontend server for feature/ui in its own worktree and keep it running while you work on other features, then reattach to verify logs.
Quick Start
Use gwq tmux run with a worktree pattern and a command, then verify with gwq tmux list and attach using gwq tmux attach <pattern>.
Examples:
gwq tmux run -w feature/ui "npm run dev"
gwq tmux run -w feature/api "go run main.go"
gwq tmux list
gwq tmux attach feature/ui