| name | ship |
| description | Prepare deploy, pull request, or release readiness. Use when packaging completed work for review, release, deployment, handoff, final quality gates, TDD evidence review, security checks, or PR preparation. |
SHIP
Use this skill to prepare completed work for delivery.
For detailed Codex submission mechanics, read references/workflow.md.
Inputs
AGENTS.mdprodops/artifacts/plans/reliability/prodops/artifacts/trails/sessions/ (active session trail)prodops/framework/journeys/delivery/phases/finish/quality-gates.md- Current branch diff and validation evidence
Flow
- Confirm the change maps to the current Reliability Plan or documented
follow-up.
- Confirm the branch and diff against the intended base.
- Verify TDD evidence for behavior changes.
- Run final quality gates: format, lint, build and tests appropriate to the
changed files.
- Run security checks for secrets, unsafe config, dependency changes and
accidental environment leakage.
- Review the diff as if doing code review.
- Summarize changed behavior, impacted artifacts and deployment risk.
- Identify rollback, monitoring and operational notes when applicable.
- Prepare PR or deploy notes.
- Append shipping evidence to the Release Trail.
Guardrails
- Do not ship undocumented behavior changes.
- Do not present missing evidence as complete.
- Do not change business scope during ship preparation.
- Do not include unrelated changes in the PR or deployment package.
- Do not commit secrets, real tokens, personal credentials or local-only paths.
- Tests must cover changed behavior or the residual test gap must be explicit.
- Behavior changes must show TDD evidence or explain why TDD was not applicable.
- PR or deploy notes must explain behavior, validation and risk.
Engineering References
