vibecode-production-qa-validator
13-phase production QA for fullstack Next.js apps: build verification, SEO tags, OG images, favicon, route regression, API auth, page speed, lazy load, vulnerability scan, UI/UX cards, error boundaries, database, secure rendering, and cleanup.
npx skills add sickn33/agentic-awesome-skills --skill vibecode-production-qa-validator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Production QA Validator Run phases in order. Fix failures before moving to next. ## When to Use - Use before shipping or promoting a fullstack Next.js app to production. - Use after large UI, SEO, auth, API, database, or dependency changes need a concrete launch-readiness pass. - Use when you need a compact command-driven checklist for build, route, metadata, performance, security, and cleanup checks. ```bash export PROD_URL="https://yourdomain.com" export QA_AUTH_HEADER="" # optional: "Bearer eyJ..." export PAGESPEED_API_KEY="" # optional: for auto PageSpeed API ``` --- ## Consolidated Runner ```bash qa:all() { qa:code && qa:build && qa:routes / /about /contact /privacy /terms /faq /sitemap.xml /robots.txt /api/health && qa:seo && qa:api /api/health /api/tools && qa:git && qa:smoke; } qa:full() { qa:all && qa:auth && qa:auth:cookies && qa:lazyload && qa:heavyload && qa:vulns && qa:cleanup && qa:ux:cards && qa:ux:boundaries && qa:ux:animation && qa:database && qa:secure; } ``` --- ### Phase 1: Code Integrity - [ ] `npx tsc --noEmit` - [ ] `npx eslint . --ext .js,.jsx,.ts,.tsx --max-warnings 0` - [ ] `npm test -- --runInBand --passWithNoTests` ```bash qa:code() { npx tsc --noEmit
- When to Use
- Consolidated Runner
- Phase 1: Code Integrity
- Phase 2: Build Verification
- Phase 3: API Session & Authentication
- Phase 4: Route Regression
- Phase 5: SEO — Tags, Images, Favicon, Slugs
- Phase 6: API Route Behavior
- Phase 7: Git Hygiene
- Phase 8: Post-Deployment Smoke Test
- Phase 9: Page Speed, Lazy Load & Bundles
- Phase 10: Cleanup & Vulnerability Scan
- Phase 11: UI/UX — Cards, Animation, Error Boundaries
- Phase 12: Database & Data Layer
export PROD_URL="https://yourdomain.com"
export QA_AUTH_HEADER="" # optional: "Bearer eyJ..."
export PAGESPEED_API_KEY="" # optional: for auto PageSpeed API
local F=0
for ep in /api/auth/login /api/auth/session /api/auth/logout; do
curl -so /dev/null -w "%{http_code}" "$PROD_URL$ep" | grep -q "200\|401" || { echo " ✗ $ep unreachable"; ((F++)); }
done
curl -so /dev/null -w "%{http_code}" "$PROD_URL/api/protected" | grep -q "401\|403" || echo " ⚠ Protected route not denying unauthenticated"
return $F
for ep in /api/auth/session /api/auth/login; doWhat does the vibecode-production-qa-validator skill do?
13-phase production QA for fullstack Next.js apps: build verification, SEO tags, OG images, favicon, route regression, API auth, page speed, lazy load, vulnerability scan, UI/UX cards, error boundaries, database, secure rendering, and cleanup.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill vibecode-production-qa-validator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.