conductor-setup

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Conductor Setup

Conductor 配置

Use this skill when configuring a repository for Conductor workspaces. When invoked directly, audit the setup against the conventions below and either apply the changes or report that none are needed.

当为Conductor工作区配置仓库时使用此技能。直接调用时，根据以下约定检查现有配置，要么应用所需更改，要么报告无需修改。

Workflow

工作流程

Inspect
```
.conductor/settings.toml
```
,
```
.conductor/settings.local.toml
```
, legacy
```
conductor.json
```
,
```
.worktreeinclude
```
,
```
.conductor/*.sh
```
, legacy root-level
```
conductor-*.sh
```
, package scripts, and repo docs. Check
```
CONDUCTOR_IS_LOCAL
```
and decide whether each script supports local workspaces, cloud workspaces, or both.
Read only the references needed for the task:
- ```
references/settings-and-migration.md
```
  for settings layers, schemas, supported repository fields, or
```
conductor.json
```
  migration.
- ```
references/scripts-and-environment.md
```
  for setup/run/archive scripts, shells, variables, concurrency, Spotlight, or caches.
- ```
references/files-layouts-and-troubleshooting.md
```
  for Files to copy,
```
.worktreeinclude
```
  , monorepos, linked repositories, MCP/privacy, or diagnosis. Read more than one only when the task crosses those concerns.
Apply the selected reference's documented contract. Prefer team settings over machine-local configuration; preserve an existing deliberate script layout; use Conductor variables instead of hard-coded workspace paths, resources, and local ports.
Keep secrets and machine-specific credentials out of committed settings. Change MCP/privacy configuration only when asked or required by repository policy.
Validate TOML and run the narrowest relevant check for every script changed. Report when the existing setup already satisfies the requested outcome.

检查
```
.conductor/settings.toml
```
、
```
.conductor/settings.local.toml
```
、旧版
```
conductor.json
```
、
```
.worktreeinclude
```
、
```
.conductor/*.sh
```
、旧版根目录下的
```
conductor-*.sh
```
、包脚本以及仓库文档。检查
```
CONDUCTOR_IS_LOCAL
```
环境变量，判断每个脚本是否支持本地工作区、云端工作区，或是两者都支持。
仅读取完成任务所需的参考文档：
- 若涉及配置层级、schema、支持的仓库字段或
```
conductor.json
```
  迁移，请查阅
```
references/settings-and-migration.md
```
  。
- 若涉及启动/运行/归档脚本、shell环境、变量、并发、Spotlight或缓存，请查阅
```
references/scripts-and-environment.md
```
  。
- 若涉及需复制的文件、
```
.worktreeinclude
```
  、单体仓库、关联仓库、MCP/隐私设置或问题诊断，请查阅
```
references/files-layouts-and-troubleshooting.md
```
  。仅当任务涉及多个相关领域时，才需要阅读多份文档。
遵循所选参考文档中记录的约定。优先使用团队配置而非机器本地配置；保留现有经过深思熟虑的脚本布局；使用Conductor变量而非硬编码的工作区路径、资源和本地端口。
请勿将密钥和机器特定凭据存入已提交的配置中。仅在被要求或仓库政策要求时，才更改MCP/隐私配置。
验证TOML文件，并对每个修改过的脚本运行最相关的窄范围检查。当现有配置已满足预期结果时，进行相应报告。

Resources

资源

```
references/settings-and-migration.md
```
: settings scope, precedence, fields, schemas, and legacy migration.
```
references/scripts-and-environment.md
```
: script roles, local/cloud shells and variables, run behavior, caches, and cleanup.
```
references/files-layouts-and-troubleshooting.md
```
: copied files, repository layouts, privacy boundaries, and diagnosis.

```
references/settings-and-migration.md
```
：配置范围、优先级、字段、schema以及旧版迁移。
```
references/scripts-and-environment.md
```
：脚本角色、本地/云端shell与变量、运行行为、缓存及清理。
```
references/files-layouts-and-troubleshooting.md
```
：复制文件、仓库布局、隐私边界及问题诊断。