What problem does it solve? Publishing a change to this pizza production app without verifying generated API clients, typechecks, tests, workflow health, and live-data heals can silently break the browser-facing app or mutate production data. This Skill enforces a repository-specific release gate so no deploy is recommended without recorded evidence. ## Core Features & Use Cases - Required release gates: Runs generated-client freshness checks, package typechecks, unit/integration test workflows, and restarts the API and web workflows to verify the real preview path. - Conditional and destructive-test safety: Routes browser smoke, accessibility, visual, PWA, and full E2E suites based on the changed surface, and blocks destructive tests from ever touching production or shared databases. - Operational warnings and go/no-go report: Surfaces data heals, schema changes, and sync risks, then produces a structured PASS/FAIL report ending in an explicit GO or NO-GO decision. - Use Case: After changing an API route and a shared client type, ask for a release readiness check; the Skill runs the generated-client check, typechecks, relevant tests, restarts workflows, verifies the preview, and returns a NO-GO if any evidence is missing. ## Quick Start Ask the assistant to run the release checklist and tell you whether the current changes are ready to publish.
