Triage
cmd/crewship/cmd_admin_extras.go exposes the triage-rules surface: declarative classification rules the server can apply to pending issues in bulk.
crewship triage list
GET /api/v1/triage-rules. JSON-shaped output by default; structured filters via --filter.
crewship triage create
POST /api/v1/triage-rules. Creates a rule that classifies pending issues by title. A rule matches an issue title via --match-type against --pattern, then applies the configured action fields. Rules evaluate in position order during process; the first match wins.
regex pattern is compiled server-side; an invalid expression returns 400.
crewship triage update <rule-id>
PATCH /api/v1/triage-rules/{id}. Only the flags you set are sent. The same string fields as create are accepted, plus --position (reordering) and --enabled (toggle). Passing an empty string to --crew/--assignee/--project clears that field server-side.
crewship triage delete <rule-id>
DELETE /api/v1/triage-rules/{id}. Aliases: remove, rm. Prompts for confirmation unless -y/--yes is passed.
crewship triage process
POST /api/v1/triage/process with {}. Runs the processor: every enabled rule is applied to all pending issues. Returns whatever the server reports as the processed counts and per-rule outcomes.
See also
crewship issue— view the issues the triage processor acts on.crewship label— labels are the most common rule action.