deployment-audit

Audits build and deployment configuration of React/Vite apps with Node/Express backends on Google Cloud.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/danilonovaisv/DAN-IMAGES-PROMPTS-2 --skill deployment-audit-danilonovaisv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment-audit
Source: https://github.com/danilonovaisv/DAN-IMAGES-PROMPTS-2/tree/main/.agents/skills/deployment-audit
Command: npx skills add https://github.com/danilonovaisv/DAN-IMAGES-PROMPTS-2 --skill deployment-audit-danilonovaisv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a React/Vite frontend with a Node/Express backend to Google Cloud, Firebase App Hosting, or Cloud Run often fails due to misconfigured runtime environment variables, leaked secrets, missing health checks, or reliance on ephemeral filesystem storage. This Skill provides a structured audit procedure to catch these issues before and after rollout. ## Core Features & Use Cases - Build and Entrypoint Verification: Confirms the Vite build outputs dist and that the production server serves the expected assets with correct PORT, 0.0.0.0 binding, and health checks. - Secrets and Environment Separation: Ensures public VITE_* variables are separated from server-side secrets and that no sensitive API keys are exposed in client-side variables. - Persistence and Rollback Validation: Verifies durable data does not depend on the instance filesystem, runs smoke tests on health and CRUD flows, and documents rollback steps. - Use Case: Before promoting a new release to Cloud Run, run the audit to confirm runtime env vars and secrets are set on the target service, then smoke test the health endpoint after rollout. ## Quick Start Audit my React/Vite and Express app deployment to Cloud Run and verify environment variables, health checks, and persistence before rollout.

Frequently Asked Questions about deployment-audit

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

FAQPage Schema
How do I audit a Vite and Express app before deploying to Cloud Run?▼

Check package.json build and start scripts, confirm the Vite build generates dist and the production server serves it, verify PORT binding on 0.0.0.0 with a health check endpoint, then smoke test health and CRUD flows after rollout.

Why should API keys not be placed in VITE_* environment variables?▼

VITE_* variables are bundled into the client-side JavaScript and are publicly visible in the browser. Sensitive API keys must remain as server-side secrets configured on the target service such as Cloud Run or Firebase App Hosting.

Does this audit work with Firebase App Hosting and Google Cloud Run?▼

Yes, the procedure covers both Firebase App Hosting and Cloud Run as deployment targets. It emphasizes identifying the real deploy target first and confirming runtime variables and secrets on that specific service.

Why does my app lose data after redeploying to Cloud Run?▼

Cloud Run instances have ephemeral filesystems, so any data written locally is lost on redeploy or scaling. Durable data must be stored in an external database or managed storage service instead of the instance filesystem.

What should I check after a deployment rollout completes?▼

Run smoke tests against the health check endpoint and exercise the core CRUD flow to confirm the service works end to end. Also document a rollback path to the previous revision in case issues appear.