deploy-verify
SolidPost-deploy smoke test combining all 5 tools (Sentry + Supabase + Firecrawl MCPs, plus the Langfuse and Playwright CLIs) into one workflow. Auto-detects deployment context, checks Sentry for new errors (with Seer AI root-cause on P0s), verifies Supabase migration health and logs, confirms Langfuse trace pipeline, runs Playwright smoke test on critical paths, and produces a ship-or-rollback verdict. Works with any project. Use when asked to: "verify deploy", "post-deploy check", "smoke test production", "check if deploy is healthy", "ship or rollback", "post-release check", "verify release", "deploy health check", or "run post-deploy".
Install
Quality Score: 82/100
Skill Content
Details
- Author
- kensaurus
- Repository
- kensaurus/cursor-kenji
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
deploy-verify
Post-restart proof that the SPECIFIC change you just shipped is the code now serving traffic — not just that the service is up. Runs data-driven assertions (health body, grep the live file for your wiring, import the new module in the service env, grep the SERVED HTTP asset, scan journal for errors since restart) and returns one PASS/FAIL verdict. Use after any deploy/restart, when Ian says "did it go live", "verify the deploy", "is my change live", "confirm it shipped", or to prove a fix in the running product (not code-trace).
pre-deploy
Run the full local verify (lint, library and package builds with the publish lint, story tests, Storybook build, website lint + build, the built-HTML validators, and the served-site checks) and confirm the site is safe to push to Vercel. Use when asked whether changes are ready to push, deploy, or ship, or for a pre-deploy check.
verify-prod-after-deploy
Run after every push that deploys to Railway — verifies the deploy actually landed AND the changed surface actually works live. Use when a push to main completes, when a deploy is claimed done, or before reporting any shipped feature as live. Green tests are not a live verification (the insider collector passed 12 tests while 403-ing on 100% of prod fetches).