pre-ship-review
Structured "what can still break" audit before marking a phase or slice complete
git clone --depth 1 https://github.com/debugbundle/debugbundle /tmp/pre-ship-review && cp -r /tmp/pre-ship-review/.agents/skills/pre-ship-review ~/.claude/skills/pre-ship-reviewSKILL.md
# Pre-Ship Review Before updating the local STATUS tracker to mark any phase or slice as complete, run this checklist. ## Checklist 1. **Inventory** — List every changed module, route, and data path in this slice. 2. **Failure modes** — For each: what happens under bad input, concurrency, partial failure, edge-case state? 3. **Trust boundaries** — Does untrusted data cross into privileged contexts anywhere? 4. **Resource cleanup** — Leaked connections, orphaned files, dangling references? 5. **Contract alignment** — Does the implementation still match `/contracts/` and `/spec/`? 6. **Test coverage** — Are all changed paths covered? Any missing edge-case tests? 7. **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? ## Rules - 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.
Use DebugBundle MCP and CLI workflows to investigate runtime errors/failures, fetch bundles, manage operational debugging surfaces, run verification, and guide fixes when captured operational evidence is relevant.
Use this skill for any UI, UX, layout, interaction, component, accessibility, or design-system related task. It helps choose familiar patterns, preserve system consistency, and avoid low-quality generated UI.
Mandatory documentation sync after a phase ships
Ensure clean session continuity when context is getting long or session is ending
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".