agent-workspace

Create isolated branch-scoped workspaces using git worktree and tmux.

Updated Jul 10, 2022
One-click install
npx skills add https://github.com/samuerio/.dotfiles --skill agent-workspace-samuerio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-workspace
Source: https://github.com/samuerio/.dotfiles/tree/main/agents/skills/agent-workspace
Command: npx skills add https://github.com/samuerio/.dotfiles --skill agent-workspace-samuerio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create isolated, branch-scoped development workspaces by integrating git worktree and tmux to streamline context switching and focused coding sessions.

Core Features & Use Cases

  • Branch-scoped workspaces that can be created or switched with a single command.
  • Automatic tmux session management and window layout for each workspace.
  • Output reporting for branch and worktree paths to support automation and orchestration.

Quick Start

Run the create_workspace.sh script with an optional branch argument to create an isolated git worktree and tmux session.

Frequently Asked Questions about agent-workspace

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

FAQPage Schema
How do I create an isolated git worktree with a tmux session for a specific branch?

You can create an isolated git worktree with a tmux session by running a script that automates branch-scoped workspace creation, generating a dedicated worktree path and launching a corresponding tmux session for focused development.

What is a branch-scoped workspace and when do I need git worktree and tmux?

A branch-scoped workspace is an isolated development environment combining a git worktree and tmux session. You need this when context switching between branches interrupts coding sessions and you want to maintain separate window layouts per branch.

Do I need git and tmux installed to automate branch workspace creation?

Yes, you must have both git and tmux installed on your system. The automation script requires these dependencies to create the worktree and manage the tmux session, and it must run inside an existing git repository.

What's the best way to switch between branch-oriented development environments?

The best way to switch between branch-oriented environments is using an automated script that applies git worktree and tmux integration, allowing you to switch to a specific branch workspace with a single command while preserving your tmux window layout.

Can I use branch workspace output for downstream automation and orchestration?

Yes, the workspace creation process reports the resulting branch name and worktree path as output. You can feed these values directly into downstream automation pipelines and orchestration tools to chain subsequent development tasks.

Why does my git worktree tmux workspace creation fail outside a git repository?

Workspace creation fails outside a git repository because the script depends on existing git repository infrastructure to create the worktree. You must navigate into a valid git repository directory before executing the workspace creation command.