ship - Pull Request Stage
Invariants
- Ship only approved and documented tasks.
- Run available pre-ship checks before creating a pull request.
- Do not auto-merge.
- Keep released-version work for the
releasestage.
Runtime adapters may expose this stage as a slash command, menu action, or natural-language skill invocation. The portable stage name is ship.
Workflow
- Read
AGENTS.md. - Resolve the task ID and read the task document.
- Verify the task is in
ApprovedinTASKS.md. - Confirm feature docs and test report exist where applicable.
- Run pre-ship checks documented by the project or task.
- Review changed files for unintended edits and secrets.
- Create or reuse an appropriate branch.
- Create a pull request with links to the task document and test report.
- Move the task to
Ready To ShipinTASKS.md.
Pre-Ship Checks
Run available project checks, such as:
pnpm build
pnpm typecheck
pnpm lint
pnpm test
Use the commands that exist in the target project. If a command is unavailable, record that it was skipped and why.
Pull Request Body
## Summary
- {Change summary}
## Verification
- {Command or report}
## Workflow References
- Task: docs/task/{ID}-{task-name}.md
- Test report: docs/testing/{ID}-{task-name}.md
- Feature docs: {path or N/A}
Handoff
Ship preparation complete for task {ID}
Task status: Ready To Ship
PR: {url}
Next stage after merge: release