Ship

<!-- requires: tester --> <!-- chains: /critique --> <!-- generated from .ai/workflows/ship.md; do not edit directly -->

Codex: this skill is the /ship adapter. For chained workflows (/critique), invoke the matching generated skill (for example heph:<workflow>) when it is available; otherwise read and follow .agents/skills/<workflow>/SKILL.md. Use Codex role agents from .codex/agents/ when the runtime exposes them; otherwise perform the work directly and keep the same structured output.

Codex does not substitute $ARGUMENTS — read it as the arguments given in the user's request.

Prepare, validate, and ship the current work. Issue number to close (optional): $ARGUMENTS

PRs must be merge-ready — all gates pass before creation, auto-merge after.

Pipeline

1. Detect repo

Run git remote get-url origin to identify the target repo.

2. Pre-push critique gate → /critique

Run /critique (Code Critique mode auto-detects on uncommitted/staged changes; the reviewer role agent absorbs the verbose diff context). This is the last quality check before the code goes out.

• FAIL: Fix blocking issues, re-run /critique (max 3 iterations). If still FAIL:
  • Separate fixable issues from fundamental design problems
  • If fixable: attempt one more targeted fix cycle
  • If fundamental: create a draft PR (--draft) with [BLOCKED] prefix, list unresolved issues in the body, file a follow-up issue, and proceed to wind-down
• PASS WITH CHANGES: Fix blocking issues, proceed
• PASS: Proceed

3. Run all quality gates in parallel

Launch as parallel role agents:

• Tests: run per project CLAUDE.md (test command, lint command, build command). If CLAUDE.md has no "Development Commands" section, infer commands from project manifests (package.json, Makefile, pyproject.toml, go.mod, etc.), mark each gate INFERRED in the report, and note the gap in the PR body.
• Git state: git status (all staged) + detect base branch (BASE=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||' || git remote show origin 2>/dev/null | awk '/HEAD branch/{print $NF}' || echo master)), then git log --oneline origin/$BASE..HEAD (commits ready)

If any gate fails:

• Analyze root cause — don't blindly re-run
• Fix and re-run (max 2 cycles)
• If a gate still fails after retries:
  • If it's lint: auto-fix what you can, note remaining issues in PR body
  • If it's tests: create PR as draft with [FAILING: <test-name>] prefix and failure analysis
  • If it's build: this is a hard stop — do not create a PR with a broken build. Commit progress, file follow-up issue.

4. Update docs

• Record the change. If changelog.d/ exists, write one fragment per PR: changelog.d/<issue-or-slug>.<added|changed|fixed|removed>.md, containing the entry body without the leading - . Distinct filenames mean parallel branches never collide. Otherwise append under ## Unreleased in CHANGELOG.md.
• Commit doc changes

5. Push and create PR

git push -u origin HEAD

gh pr create --repo <detected-repo> \
  --title "<concise title>" \
  --body "$(cat <<'EOF'
## Summary
- <bullet 1>
- <bullet 2>

## Assumptions Made
- <any assumptions made during autonomous operation, or "None">

## Quality gates
- [x] All tests passing
- [x] Lint clean
- [x] Code critique: PASS
- [x] No regressions

## Known Limitations
- <any documented caveats from critique loops, or "None">

Closes #<issue number if provided>
EOF
)"

For gates that passed with caveats, use [x] with a suffix: - [x] Lint clean (with caveats — see Known Limitations).

Evidence gate — before running gh pr create, verify the composed body: no unchecked - [ ] items, no surviving <angle-bracket> placeholders, and every [x] quality-gate line corresponds to a gate actually run in this session (a claimed gate with no run behind it is a violation). On violation: run the missing gate or fix the body — never ship a checklist that claims what didn't happen.

6. Auto-merge

gh pr merge --squash --auto

Read back what happened — where the base branch requires no status check, --auto has nothing to wait on and the command succeeds by merging on the spot:

gh pr view <pr-number> --repo <detected-repo> --json state,autoMergeRequest

• OPEN with autoMergeRequest set — armed as intended; it merges when checks pass.
• MERGED — it merged immediately. Step 3's local gates were the only thing between this branch and the base, and CI gated nothing. Report that rather than "auto-merge enabled", and name the cause: the base branch requires no status checks.
• Command failed, or any other state (branch protection, required reviewers) — do NOT retry or force-push. Note that manual merge is required. This is a valid stopping point; the work is preserved in the PR.

7. Return the PR URL.

Next steps

• Run /test-issue to verify CI status if needed
• Run /finish <#> after merge to close the issue, clean up branches, and file follow-ups
• Or run /orient to see what's next