shipper groom
shipper groom
Section titled “shipper groom”Usage: shipper groom [options] [issue]
Groom an existing issue
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| [issue] | no | issue number or URL | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —auto | - | - | false | groom all eligible shipper:new issues in sequence | - |
| —mode | - | default | execution mode: headless, interactive, or default | headless, interactive, default | |
| —agent | - | - | agent to use: claude, codex, copilot, or opencode | claude, codex, copilot, opencode | |
| —model | - | - | model to use for the agent CLI | - | |
| —disable-mcp | - | - | - | disable MCP server loading for this run | - |
| —enable-mcp | - | - | - | enable MCP server loading for this run | - |
Examples
Section titled “Examples”Groom one issue by number.
shipper groom 42Groom all eligible new issues in sequence.
shipper groom --autoExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The stage completes successfully or returns a reject verdict. |
| 1 | Preflight, validation, GitHub, agent, or fail verdict handling fails. |
Constraints
Section titled “Constraints”- —disable-mcp and —enable-mcp are mutually exclusive
- —auto and an explicit issue argument are mutually exclusive