init-config

init-config

You write a crew.config.yaml at the repo root so crew is tuned to this project. Config is optional — crew works without it — but a config makes label names, guardrails, and commands explicit.

1. Don't clobber

If crew.config.yaml already exists at the repo root, do not overwrite it. Show the user the current contents and offer to adjust specific fields instead.

2. Detect the stack

Run the resolver to see what crew would auto-detect (commands, docs index):

python3 "${CLAUDE_PLUGIN_ROOT}/lib/load_config.py"

Also glance at the repo: package manager / build files, where docs live, and whether the project uses non-default GitHub label names (gh label list).

3. Write the config

Start from the annotated template and fill in what you detected:

cp "${CLAUDE_PLUGIN_ROOT}/templates/crew.config.example.yaml" crew.config.yaml

Then edit crew.config.yaml to reflect this repo:

• project.name and project.docs_index (real values, or remove docs_index to let crew auto-detect).
• commands.{install,lint,typecheck,test} — the project's real commands (drop keys the project doesn't have rather than leaving wrong values).
• labels.* — only if the repo uses non-default label names.
• guardrails.protected_paths — add this repo's sensitive areas (DB schema migrations, infra, secrets, generated code). The default ships **/migrations/**, but DB migrations are named differently across tools — detect this repo's actual mechanism and add the matching glob: e.g. Liquibase uses **/changelog/** or **/db/changelog/** (and *.changelog.* / changesets), Flyway **/db/migration/**, Rails/Django/Alembic **/migrations/**, golang-migrate **/migrate/**. Match the directory the repo actually uses; don't add a bare **/changelog/** that would also catch a docs CHANGELOG.md. If unsure, glob to the real path you find.
• mode — leave auto unless the team wants to pin github or local.
• local.isolation — leave auto (jj if installed, else kosho, else native git worktree); pin it only if the team standardizes on one. Note that jj/auto will colocate jj at the repo root (.jj/ beside .git/) on first local-mode run if it isn't already.
• Leave orchestrator, team, knowledge, ledger at defaults unless the user wants otherwise.