pre-deploy

Runs the full local verify pipeline to confirm a Next.js site is safe to push to Vercel.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill pre-deploy-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-deploy
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/pre-deploy
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill pre-deploy-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before pushing changes to Vercel, you need confidence that lint, type-checks, builds, accessibility tests, and served-site checks all pass locally. This Skill runs the same verification chain as CI and reports exactly which step failed and why, so broken deploys never reach production. ## Core Features & Use Cases - Full local verify: Executes npm run verify covering ESLint, the library type-check, the publishable npm package build, Storybook story tests with axe accessibility assertions, the Storybook build, and the Next.js website lint and build. - Post-build validation: Runs built-HTML validators and served-site checks including a real-browser hydration smoke test and page-level axe passes in both themes. - Failure diagnosis: Identifies the failing step, distinguishes render errors from a11y violations and play-function assertion failures, and reports exact error messages with file paths. - Use Case: After refactoring a portal-based component like AlertDialog, ask whether the changes are ready to push; the Skill runs the verify chain and flags any SSR-unsafe code or static generation failures before you ship. ## Quick Start Ask the AI to run a pre-deploy check and confirm whether the current changes are safe to push to Vercel.

Frequently Asked Questions about pre-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my changes are ready to push to Vercel?

Run the pre-deploy check, which executes npm run verify from the repo root. It mirrors the CI pipeline: lint, type-check, library and package builds, story tests, Storybook build, website build, and served-site checks, then reports whether it is safe to push.

How to run the same checks locally that CI runs?

Use npm run verify at the repo root. It mirrors the CI jobs in .github/workflows/ci.yml minus documented CI-only exceptions, so a green local verify closely predicts a green CI run.

Why does my Next.js build fail with prerendering errors?

Static generation failures usually come from SSR-unsafe code, such as portal components referencing document at module scope or missing "use client" directives on components using browser APIs. The pre-deploy check watches for these patterns and reports the failing page.

Does the verify pipeline include accessibility testing?

Yes. Every Storybook story is rendered in headless Chromium with axe asserting WCAG 2.1 AA, and served pages get a page-level axe pass in both themes. Contrast checks are deliberately excluded from the gate.

When should I run Chromatic visual regression tests?

Dispatch the Chromatic workflow with gh workflow run chromatic.yml whenever changes touch component CSS, src/tokens/, or .storybook/. Text-only or script-only changes do not need a run, since each run consumes cloud snapshot budget.

Can this skill push my changes after verification passes?

No. The skill only runs checks and reports results; pushing remains a manual decision. It confirms whether the build is safe to ship but never performs the push itself.