shipper init
shipper init
Section titled “shipper init”Usage: shipper init [options]
Initialize shipper in the current repository
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| None | - | - | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —agent | - | - | coding agent to use (claude, codex, copilot, or opencode) | - | |
| —autocommit | - | - | - | stage and commit .shipper/ after writing files | - |
| —push | - | - | - | push the commit to the remote (requires —autocommit) | - |
Examples
Section titled “Examples”Initialize Shipper in the current repository.
shipper initExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | Repository configuration files are written successfully. |
| 1 | Validation, setup, git commit, or git push fails. |
Constraints
Section titled “Constraints”- —push requires —autocommit
- When neither —agent nor a valid stored agent is available, interactive init shows a numbered agent menu: 1. Claude Code, 2. Codex CLI, 3. Copilot CLI; enter 1, 2, 3, or a supported agent name.
- In interactive agent selection, bare Enter, unrecognized names, and out-of-range numbers abort init.
- shipper init owns committed .shipper/ artifacts in this repository; rerun it and commit the resulting .shipper/ changes when the init drift guard reports drift
- For the files and directories written by shipper init, see .shipper directory.
- Troubleshooting: missing or duplicate workflow labels
- Troubleshooting: CLI version drift and version mismatch