Ship check
A short gate before code leaves your hands. Don't declare done until it passes.
Steps
- Review the diff. Invoke the
code-reviewskill (mattpocock-skills) on the change, or run the/code-reviewcommand. Fix real findings before shipping. - 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.
- Docs & memory. Confirm
keep-documentationand (if architecture changed)keep-architectureare satisfied. Record any durable decision in project memory. - Scope. Confirm the diff matches the agreed brief — nothing snuck in, nothing half-done.
- 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.