ship
/ship
Finish already-implemented work for merge or release - verify before claiming done, write commits and PR descriptions, plan releases and rollbacks. Use when wrapping up a branch or deciding how to integrate it. Not for writing code.
- Author
- asmn-96 ↗
- Repository
- ai-agents-skills-toolkit ↗
- Licence
- MIT
- Last repository change
- 27.09.2026
Assessment and security
- Files in this package
- 7
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Finish already-implemented work for merge or release - verify before claiming done, write commits and PR descriptions, plan releases and rollbacks. Use when wrapping up a branch or deciding how to integrate it. Not for writing code.
Original author description
Finish already-implemented work for merge or release - verify before claiming done, write commits and PR descriptions, plan releases and rollbacks. Use when wrapping up a branch or deciding how to integrate it. Not for writing code.
How it works
- 1. Verify before any completion claim
- 2. Decide how to integrate
- 3. Write the artifacts
- Precedence (overrides upstream text)
- Output
SKILL.md preview
---
name: ship
description: Finish already-implemented work for merge or release - verify before claiming done, write commits and PR descriptions, plan releases and rollbacks. Use when wrapping up a branch or deciding how to integrate it. Not for writing code.
license: MIT
---
# Ship route
Finish work that is already implemented: verify it, decide how to integrate it, and describe it honestly. This route never edits application code — it verifies, commits, and describes.
Paths below are relative to this skill's folder (in Claude Code: `${CLAUDE_SKILL_DIR}`).
## 1. Verify before any completion claim
Read `upstream/verification-before-completion/UPSTREAM.md` and follow its Iron Law: no completion claim without fresh verification evidence run in this session. Before saying tests pass, a build succeeds, or a bug is fixed, identify the command that proves it, run the full command now, and read its actual output. A prior run, "should pass," or an agent's self-report is not evidence.
## 2. Decide how to integrate
Read `upstream/finishing-a-development-branch/UPSTREAM.md` and follow its flow: verify tests first (stop and report failures if they fail — do not proceed to the menu), detect whether this is a normal repo, a named-branch worktree, or a detached HEAD, confirm the base branch, then present the matching options menu and wait for the human's choice before merging, pushing, or discarding anything.
## 3. Write the artifacts
- Commit messages and PR descriptions: use `references/pr-description.md`. The "How verified" section is mandatory and must name real command output, including anything skipped.
- Release notes and rollback planning, especially for schema/migration/flag-sensitive changes: use `references/release-checks.md`.
## Precedence (overrides upstream text)
- The project's own scripts and CI define "verified," not this skill's judgment. If the project has a test/build/lint command, run that command — do not substitute a partial check.
- Upstream's discard-the-work path in `finishing-a-development-branch` only ever runs on an explicit, exact request from the human (the literal word "discard" per upstream's confirmation step). Never infer consent to discard, merge, push, or force-push from enthusiasm or vague agreement.
- Remove only worktrees this session created; leave host-managed ones (for example `.claude/worktrees/`) in place.
- Never force-push, skip hooks, or push to the default/shared branch unless the human explicitly asks for that specific action in this conversation. If asked to force-push to main or skip a failing check to unblock a merge, refuse and propose the safe path instead (fix the failure, or push a new branch and open a PR).
- Code review of the diff itself belongs to the `review` route; security sign-off (auth, secrets, dependency, supply-chain risk) belongs to the `secure` route. This route may point to them but does not replace them.
- Never claim a test, build, browser check, or scan passed unless its output is in this session. If something was not run, say so in the report instead of assuming it would pass.
## Output
- State of verification: what ran, what passed/failed, what was skipped, with actual output or counts — not adjectives.
- The integration menu from `finishing-a-development-branch/UPSTREAM.md`, and the human's choice once given.
- A PR description or commit message using `references/pr-description.md` when one is needed.
- For anything release-shaped (new column, new flag, schema change, production impact): rollback path and monitoring plan from `references/release-checks.md`.
Files in this package (7)
- SKILL.md 4 KB
- references/pr-description.md 1 KB
- references/release-checks.md 3 KB
- upstream/finishing-a-development-branch/LICENSE 1 KB
- upstream/finishing-a-development-branch/UPSTREAM.md 8 KB
- upstream/verification-before-completion/LICENSE 1 KB
- upstream/verification-before-completion/UPSTREAM.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · asmn-96/ai-agents-skills-toolkit | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| namedtoaster/the-last-mile | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| zahidakhyar/skills | 100 | MIT |
| NolwennD/gabier | 100 | Apache-2.0 |
| mgiovani/cc-arsenal | 100 | MIT |
Database snapshot: 13.11.2026 · package version 9b8a50a3fcce (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100release-engineering
This skill should be used when cutting a release — computing a semver bump from conventional commits, writing changelogs and release notes, sequencing breaking changes, and planning rollbacks. - 90finish
Land completed work — verify tests, present options (merge/PR/keep/discard), execute chosen workflow. Auto-triggered after implementation and review pass. Also available as /finish. - 95handoff
Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery. - 100ship-it
Use when finished work should be taken all the way to a fully reviewed, merge-ready PR in one pass. Does not merge; the author keeps merge authority (see /lgtm or /yolo to merge). - 100ship-it
Use when finished work should be taken all the way to a fully reviewed, merge-ready PR in one pass. Does not merge; the author keeps merge authority (see /lgtm or /yolo to merge). - 100prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.