conductor-setup
Skill1 starsChanged 10 months agoMITView on GitHub
Configure a Rails project to work with Conductor (parallel coding agents)
- Reads credentials
- Installs packages
11 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- lgzarturo/codeconductoredited, first seen Oct 18, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- oddradiocircle/conductor-portabletheir own version, first seen Aug 16, 2026
- biw/skillstheir own version, first seen Aug 15, 2026
- gemini-cli-extensions/conductortheir own version, first seen Jul 14, 2026
- magnusrodseth/dotfilestheir own version, first seen May 26, 2026
Used with
Projects with it also use conductor-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
airclearSkillconductor-review
Acts as a Principal Software Engineer and Code Review Architect to review completed or in-progress work against project standards, style guides, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track.
Also in 4 projects that use this
Other versions11 projects use a version of this.
Word for word · 1
- VALL-dikss/skills★ 1100% same
Edited · 2
- jornalistainclusivo/jinc-skills★ 179% same
- lgzarturo/codeconductor★ 079% same
Wrote their own version · 8
- gemini-cli-extensions/conductor★ 3.7ksame name
- hlhr202/Conductor-for-all★ 52same name
- xfstudio/skills★ 9same name
- magnusrodseth/dotfiles★ 3same name
- ai4brands-design/claude-skills★ 2same name
- airclear/skills★ 2same name
- biw/skills★ 2same name
- oddradiocircle/conductor-portable★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- buildSkill
- faviconSkill
- issuesSkill
- new-rails-projectSkill
- readmeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 6 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Create conductor.json in the project root if it doesn't already exist:
- Very specific: line 28
Create bin/conductor-setup if it doesn't already exist:
- Very specific: line 49
Create the script directory if needed, then create script/server if it doesn't already exist:
- Distinctive: line 75
If this file exists and configures Redis, update it to use:
- Distinctive: line 81
If this file exists, update the development adapter to use:
- Distinctive: line 89
If this file configures Redis for caching, update to use:
- Distinctive: line 95
If this file exists and configures a Redis cache store, update to use:
- Very specific: line 102
Don't overwrite existing files: Check if conductor.json, bin/conductor-setup, and script/server exist before creating them.
- Distinctive: line 103
Rails config updates: Only modify Redis-related configuration.
- Very specific: line 104
Create directories as needed: Create script/ directory if it doesn't exist.
- Distinctive: line 108
After creating the files:
- Very specific: line 110
Run script/server to verify it starts without errors
- Very specific: line 111
Check that Rails configs properly reference ENV['REDIS_URL'] or ENV.fetch('REDIS_URL', ...)
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Set up this Rails project for Conductor, the Mac app for parallel coding agents.
What to Create
1. conductor.json (project root)
Create conductor.json in the project root if it doesn't already exist:
{
"scripts": {
"setup": "bin/conductor-setup",
"run": "script/server"
}
}2. bin/conductor-setup (executable)
Create bin/conductor-setup if it doesn't already exist:
#!/bin/bash
set -e
# Symlink .env from repo root (where secrets live, outside worktrees)
[ -f "$CONDUCTOR_ROOT_PATH/.env" ] && ln -sf "$CONDUCTOR_ROOT_PATH/.env" .env
# Symlink Rails master key
[ -f "$CONDUCTOR_ROOT_PATH/config/master.key" ] && ln -sf "$CONDUCTOR_ROOT_PATH/config/master.key" config/master.key
# Install dependencies
bundle install
npm installMake it executable with chmod +x bin/conductor-setup.
3. script/server (executable)
Create the script directory if needed, then create script/server if it doesn't already exist:
#!/bin/bash
# === Port Configuration ===
export PORT=${CONDUCTOR_PORT:-3000}
export VITE_RUBY_PORT=$((PORT + 1000))
# === Redis Isolation ===
if [ -n "$CONDUCTOR_WORKSPACE_NAME" ]; then
HASH=$(printf '%s' "$CONDUCTOR_WORKSPACE_NAME" | cksum | cut -d' ' -f1)
REDIS_DB=$((HASH % 16))
export REDIS_URL="redis://localhost:6379/${REDIS_DB}"
fi
exec bin/devMake it executable with chmod +x script/server.
4. Update Rails Config Files
For each of the following files, if they exist and contain Redis configuration, update them to use ENV.fetch('REDIS_URL', ...) or ENV['REDIS_URL'] with a fallback:
config/initializers/sidekiq.rb
If this file exists and configures Redis, update it to use:
redis_url = ENV.fetch('REDIS_URL', 'redis://localhost:6379/0')config/cable.yml
If this file exists, update the development adapter to use:
development:
adapter: redis
url: <%= ENV.fetch('REDIS_URL', 'redis://localhost:6379/1') %>config/environments/development.rb
If this file configures Redis for caching, update to use:
config.cache_store = :redis_cache_store, { url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0') }config/initializers/rack_attack.rb
If this file exists and configures a Redis cache store, update to use:
Rack::Attack.cache.store = ActiveSupport::Cache::RedisCacheStore.new(url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0'))Implementation Notes
- Don't overwrite existing files: Check if conductor.json, bin/conductor-setup, and script/server exist before creating them. If they exist, skip creation and inform the user.
- Rails config updates: Only modify Redis-related configuration. If a file doesn't exist or doesn't use Redis, skip it gracefully.
- Create directories as needed: Create
script/directory if it doesn't exist.
Verification
After creating the files:
- Confirm all Conductor files exist and scripts are executable
- Run
script/serverto verify it starts without errors - Check that Rails configs properly reference
ENV['REDIS_URL']orENV.fetch('REDIS_URL', ...)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

