// Commit, run bin/ci, and open a PR if CI passes. Use when ready to ship changes.
Quick user-centric interview to capture requirements from a time-poor stakeholder.
Convert feature requirements into structured end-to-end test cases as JSON.
Interview me about the plan
Catch up on codebase changes by reviewing the diff from master and reading relevant spec files.
Prime yourself on a codebase by listing files and reading the README.
Reset the working directory for the next task by ensuring no uncommitted changes exist, then switching to the main branch and pulling latest.
| name | ship |
| description | Commit, run bin/ci, and open a PR if CI passes. Use when ready to ship changes. |
| argument-hint | ["optional commit message"] |
| disable-model-invocation | true |
| allowed-tools | Bash(git *), Bash(gh pr create *), Bash(bin/ci) |
git statusgit diff HEADgit branch --show-currentgit log --oneline -10Ship the current changes by following these steps in order:
If on master, create and checkout a new descriptive branch based on the changes.
Stage all changed files and create a single commit with an appropriate message. If $ARGUMENTS is provided, use it as the commit message.
Run bin/ci and wait for it to complete. This is mandatory — do not skip it.
bin/ci fails: stop here. Show the failure output and suggest fixes. Do NOT push or create a PR.bin/ci passes: continue to step 4.bin/ci already pushed the branch to origin. Create a pull request using gh pr create and return the PR URL and a brief summary of files changed eg 2 Files Changed