# Ship Check

> Pre-ship checklist before committing, opening a PR, or calling work done. Use when the user says "commit", "open a PR", "ship it", "are we done", or when you've finished an implementation. Reviews the diff and confirms docs/tests are in order before shipping.

- Skill: `soukupl/ship-check` (Agent Skill)
- Install (CLI): `npx skillmds@latest add soukupl/ship-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/soukupl/ship-check/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: soukupl (https://skillmd.com/u/soukupl)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/soukupl/ship-check

---


# Ship check

A short gate before code leaves your hands. Don't declare done until it passes.

## Steps

1. **Review the diff.** Invoke the **`code-review`** skill (mattpocock-skills) on the change, or run
   the `/code-review` command. Fix real findings before shipping.
2. **Tests.** Run the relevant tests. Report actual results — if something fails or you skipped a
   suite, say so plainly; never claim green you didn't see.
3. **Docs & memory.** Confirm `keep-documentation` and (if architecture changed) `keep-architecture`
   are satisfied. Record any durable decision in project memory.
4. **Scope.** Confirm the diff matches the agreed brief — nothing snuck in, nothing half-done.
5. **Commit / PR.** Only when asked. Write a clear message describing the *why*. If on the default
   branch, branch first. Never push, open a PR, or enable auto-merge unless the user asked.

Report what passed and what didn't — honestly, without hedging on the parts that are genuinely done.