Project setup

Not sure your project is wired up correctly? crux setup checks it and can apply safe fixes. Running it without a mode is read-only and equivalent to --check:

crux setup
crux setup --check

The command exits unsuccessfully when a contributor reports an error. Use --json for CI and coding-agent workflows: its stable report includes findings, planned actions, and application results.

Apply safe changes

crux setup --apply

Apply mode runs only safe, additive actions, in plan order, and then inspects the project again. It never automatically performs destructive migrations, paid provisioning, production mutations, or ambiguous edits; anything requiring approval stays a finding with exact remediation.

Use --cwd <path> to inspect another project root. Findings may include a docs URL, a copy-paste remediation, and a privacy-safe coding-agent prompt. They do not include environment values, credentials, or connection strings.

Safe additive setup is idempotent. A failed later action does not roll back earlier successful actions, so rerun crux setup --apply after correcting the reported problem.

Action classification and the --json report details: crux setup reference.