conductor

Manage parallel Conductor workspaces and worktrees for multi-branch development.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/Aias/dotfiles --skill conductor-aias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conductor
Source: https://github.com/Aias/dotfiles/tree/main/agents/skills/conductor
Command: npx skills add https://github.com/Aias/dotfiles --skill conductor-aias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when working inside Conductor (conductor.build): parallel workspaces/worktrees, CONDUCTOR_* env vars, workspace path under ~/conductor/workspaces, target branch for PRs/rebase/diff, Diff Viewer, archiving, one-branch-per-workspace rules, run scripts and ports, checkpoints/todos, or "which branch is the base". Pair with /git-workflows and /pr-guidelines for git and PR specifics. Triggers on Conductor, worktree, CONDUCTOR_ROOT_PATH, workspace city name, parallel agents, ⌘⇧N workspace, merge block, @todos.

Core Features & Use Cases

  • Supports per-workspace branch targeting, diff viewing, and checkpointed collaboration across multiple worktrees.
  • Coordinates parallel agents and per-workspace environments using CONDUCTOR_ROOT_PATH and CONDUCTOR_PORT ranges.
  • Integrates with git workflows and PR guidelines for safe multi-worktree operations.

Quick Start

Use Conductor to initialize a new workspace via ⌘⇧N and configure a target branch and root path for your project.

Frequently Asked Questions about conductor

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

FAQPage Schema
How do I manage parallel git worktrees for multi-branch development?

Parallel git worktrees are managed by coordinating per-workspace branches, ports, and root paths across multiple city workspaces. This allows isolated multi-branch development with targeted PR branches and diff viewing.

What environment variables do I need to configure for Conductor workspaces?

Conductor workspaces require CONDUCTOR_ROOT_PATH for workspace locations, CONDUCTOR_DEFAULT_BRANCH for target PR and rebase operations, and CONDUCTOR_PORT to assign per-workspace port ranges for parallel agents.

How does branch targeting work with parallel agents in Conductor?

Branch targeting in Conductor assigns a specific target PR branch to each isolated workspace, enabling parallel agents to operate on distinct worktrees simultaneously without conflicts, using configured environment variables.

Can I use Conductor workspaces with standard git workflows and PR guidelines?

Conductor workspaces integrate directly with git workflows and PR guidelines for safe operations. They must be paired with these processes to ensure auditable multi-worktree management and one-branch-per-workspace rules.

What is the best way to set up a new Conductor workspace?

Set up a new Conductor workspace by initializing it via the shortcut, then configuring the target branch and root path. This establishes the isolated environment needed for checkpointed collaboration and diff viewing.

Why do I need a specific base branch for my Conductor workspace?

A specific base branch is needed to determine the target for PRs, rebases, and diffs within a Conductor workspace. It ensures parallel worktree operations remain auditable and correctly isolated from the default branch.