shiplisted

## Repo state (injected before you start) - Branch: !`git rev-parse --abbrev-ref HEAD 2>/dev/null` - Status: !`git status --short` - Commits ahead of main: !`git log --oneline origin/main..HEAD 2>/dev/null | wc -l | tr -d ' '` - Pipeline configured: !`test -f "$(git rev-parse --show-toplevel 2>/dev/null)/delivery.json" && echo "yes — do step 6" || echo "no — SKIP step 6 entirely"` - Safe-outputs channel: !`test -n "$PIPELINE_SAFE_OUTPUTS" && echo "$PIPELINE_SAFE_OUTPUTS" || echo "NONE — \$PIPELINE_SAFE_OUTPUTS unset"` ## Instructions Ship the current work as a PR, following the kit's conventions exactly. `$ARGUMENTS` is an optional one-line summary — use it to seed the title/body, or infer one from the diff if empty. 1. **Confirm you're on a proper feature branch** (`<type>/<short-kebab-desc>`), not `main`/`master`. If on `main`, stop and tell the user to branch first — the hooks will block a commit anyway. 2. **Stage** the relevant files explicitly (never `git add -A` — see the kit's generated-file lesson). 3. **Write the commit message to a scratch file** and commit with `git commit -F` (not `-m` — long text goes through files, per the prose-vs-operation convention). Conventional prefix (`feat:`/`fix:`/`chore:`/`refactor:`/`docs:`); end the body with the `Co-Authored-By:` line the repo uses. 4. **Push** the branch (`git push -u origin <branch>`). 5. **Write the PR body to a scratch file** — 2–3 sentence what/why, one-line bullets, one verification l