Pre ship review

Structured "what can still break" audit before marking a phase or slice completeFrom its SKILL.md

Install

npx -y skills add debugbundle/debugbundle --skill pre-ship-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

1.4 KB, as published. Nobody here has run it

Before updating the local STATUS tracker to mark any phase or slice as complete, run this checklist.

Inventory — List every changed module, route, and data path in this slice.
Failure modes — For each: what happens under bad input, concurrency, partial failure, edge-case state?
Trust boundaries — Does untrusted data cross into privileged contexts anywhere?
Resource cleanup — Leaked connections, orphaned files, dangling references?
Contract alignment — Does the implementation still match /contracts/ and /spec/?
Test coverage — Are all changed paths covered? Any missing edge-case tests?
Schema/deploy safety — If this slice touches database shape or schema-dependent runtime behavior, does it use a real forward migration, does deploy run that migration before new code starts, and is any destructive cleanup deferred to a later release?

If any issue is found, fix it before marking green.
This is not optional polish — it is the final gate before a slice ships.
Do not skip this review under time pressure.
Post-production slices that change the database must explicitly reject bootstrap-as-migration shortcuts and destructive-in-place schema edits.