showdar-shiplisted

# Showdar Ship ## Purpose `showdar-ship` is a delivery-verification skill. Its normal job is to decide whether the requested change is safe to hand off, merge, package, publish, or release, using fresh local evidence and repository-defined checks. It may inspect existing release, deployment, and CI configuration as evidence. It does not create or modify that infrastructure in its normal verification mode. A readiness report is not an instruction to deploy. ## When to use - Verifying a completed change before handoff or merge. - Assessing release readiness for a web, backend, mobile, Docker, or desktop artifact. - Checking package/export/type/build metadata before a requested handoff. - Reviewing existing release or CI configuration for canonical commands and gaps. - Verifying an explicitly requested deployment, store submission, or release execution. ## When not to use - Routine implementation, debugging, code review, or test-strategy work. - Creating CI/CD, deployment, release, secrets, or environment infrastructure. - Treating “ship”, “release checklist”, or “is this ready?” as permission to deploy or publish. - Requiring a deployed endpoint when local artifact and repository checks answer the request. ## Inputs and assumptions - The requested outcome and whether it explicitly names release/deployment execution. - Current Git/worktree state and the exact change or artifact under review. - Repository-owned test, typecheck, lint, build, package, and smoke commands. -