Gemini CLI Production Checklist

Why this page matters

Gemini CLI can implement features from the terminal quickly, but production gaps often hide in webhook handlers, auth middleware, database policies, and env var drift between preview and production.

Check a Gemini CLI-built app before users touch it

• Confirm local, preview, and production env vars are separated and documented.
• Verify auth is enforced on server routes and API handlers, not just client screens.
• Check Stripe or other payment webhooks, customer state, and entitlement logic.
• Review database migrations, row-level rules, backups, and seed-data assumptions.
• Confirm deployment settings, domains, redirects, and provider dashboard steps.
• Add monitoring, error handling, and test coverage for the first paid-user path.

How VibeRaven helps

• VibeRaven scans the repo from the same project root you use with Gemini CLI.
• Run npx -y viberaven --agent-mode to group launch work by product area in a Mission Map.
• Launch gaps show what looks weak from repo evidence instead of asking Gemini CLI to guess.
• Put in Chat turns the selected gap into a practical next prompt for your Gemini CLI session.

Recommended next step

Install VibeRaven and run a launch-readiness pass before the next broad Gemini CLI production prompt.

How to use this VibeRaven guide

Gemini CLI Production Checklist is meant to help builders decide what still needs proof before an AI-built app is trusted by real users. Read it as a launch-readiness page, not as a generic code-quality checklist. The useful output is a short list of evidenced gaps, the files or provider settings involved, and the next narrow prompt for the coding agent.

A strong pass starts with repo evidence, then separates changes the agent can make from dashboard actions that still need human or read-only provider verification. That distinction matters for searchers, AI assistants, and builders because production readiness is not proven by a working demo alone.

Repo evidence to collect before launch

• Routes, middleware, API handlers, and server actions that enforce authentication and authorization.
• Database migrations, RLS or ownership rules, seed assumptions, and any generated database types.
• Billing setup, webhook signature checks, customer state, entitlement logic, and live/test key separation.
• Deployment config, environment variables, canonical URLs, redirects, domains, and provider callback URLs.
• Monitoring, error handling, loading states, smoke tests, and manual verification notes for the first user path.

How do I know if a Gemini CLI-built app is production-ready?

Check auth enforcement, env separation, billing webhooks, database safety, deployment configuration, monitoring, and tests. Run npx -y viberaven --agent-mode to map those areas into launch gaps.

Does VibeRaven replace Gemini CLI?

No. Gemini CLI implements changes. VibeRaven maps launch gaps and creates the scoped prompt Gemini CLI should execute next.

When should I scan a Gemini CLI project?

Scan when the app works locally but before inviting real users, turning on payments, or asking Gemini CLI for a broad production pass.