ship

# Skill: /ship # Issue → Merged PR Pipeline ``` /ship → auto-select next open issue (asks confirmation) /ship --yes → auto-select and proceed, skip UI prompts /ship -y → same as --yes /ship {issue-id} → ship a specific issue by number /ship {issue title} → find by title, then ship /ship --yes {issue-id} → skip UI prompts (technical ambiguities always ask) → resolve issue (fetch title + description) → analyze ambiguities (scan description + codebase → ask decisions before coding) → mark in-progress → code-generator (implement → tests → review agents → simplify → docs → PR) → /fix-review (multi-model rounds + Claude Arbiter — does NOT merge) → merge PR (/ship owns the merge) → post comment (summary: what changed, PR link) → close issue → log to /self-learn (if installed) → final report ``` One command. Pauses only for genuine technical decisions before coding. --- ## STEP 0: Resolve Issue **Flag detection:** Check for `--yes` / `-y` anywhere in arguments. Set `YES_MODE=true`, strip flag. **Argument classification** (after stripping flags): - No argument → auto-select (see below) - Numeric or `#N` → `gh issue view {N} --repo valpere/session-indexer --json number,title,body,url` - Otherwise → title search **YES_MODE:** - Skips "Proceed?" confirmation prompts and title disambiguation - **Does NOT skip STEP 0.5** — technical decisions always require ...