dev-processes

Automates creating and monitoring per-project tmux sessions with named windows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers start, monitor, and manage long-running dev processes inside tmux, eliminating manual session setup and window management overhead.

Core Features & Use Cases

  • Create and manage tmux sessions per project based on the current directory.
  • Start common workflows such as dev servers, tests, and build watchers in named tmux windows.
  • Reuse existing sessions and capture output to verify progress without restarting processes.

Quick Start

Use a tmux session for the current project: SESSION="$(basename "$PWD" | tr . _)" tmux has-session -t "$SESSION" 2>/dev/null || tmux new-session -d -s "$SESSION" -c "$PWD" tmux select-window -t "$SESSION:dev" 2>/dev/null

Frequently Asked Questions about dev-processes

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

FAQPage Schema
How do I automate starting dev servers and tests in tmux sessions?

You can automate starting dev servers and tests in tmux by creating per-project sessions with named windows for dev, test, and build workflows. This Skill uses standard shell commands to spawn and manage long-running processes without manual setup.

What is the best way to manage long-running dev processes in tmux?

Managing long-running dev processes in tmux is best handled by automatically creating sessions based on the current directory and launching watchers in dedicated windows. This approach eliminates manual session setup and allows safe reuse of existing sessions.

Can I reuse an existing tmux session for a project without restarting processes?

Yes, you can reuse existing tmux sessions without restarting processes. The Skill safely checks for active sessions using tmux utilities, captures output to verify progress, and attaches to the current project's session without disrupting running dev servers or watchers.

How do I create named tmux windows for build watchers and dev servers?

To create named tmux windows for build watchers and dev servers, the Skill initializes a detached session targeting your current working directory and configures specific windows. This isolates each long-running process for organized monitoring.

Do I need any external dependencies to use tmux for local development workflows?

No external dependencies are required to use tmux for local development workflows beyond the standard tmux utility and shell commands. The Skill relies purely on native tmux utilities for session management, window creation, and output capture.

Why does my tmux session fail to switch to a specific dev window automatically?

Your tmux session may fail to switch to a specific dev window if that window has not been created yet. The Skill handles this by checking for the window and safely selecting it only if it already exists within the current project session.