From demo to production

Find code and configuration risks, with clear next steps for your coding agent.

Illustrative example · sample project

Launch review · posts-appviberaven check · run 42

1 blockerno RLS on posts

fixed by
Claude Code

75 → 95re-checked

Viberaven/posts-app/main · v0.4.1 1 blocker
repo
northfield/posts-app

DetectedReady

auth
Clerk

Callbacks matchReady

web
posts-app.vercel.app

2 env vars missingReview

database
public.posts

No RLS policyNot ready

payments
/api/stripe/webhook

Signature checkedReady

Services
cache
email
monitoring
Sentry

Not wired inReview

Last check just now · on this computer

Scan Fix Re-check Launch
supabase/migrations/0001_posts.sql
1create table public.posts (
2 id uuid primary key,
3 user_id uuid,

no RLS: check access
for roles with write grants

fixed in 0002 · re-checked ✓

Your stack

Reads the stack you already ship on

The check

Reads, finds,
hands it over

  1. 01
    Reads your stack

    From the files you already have

  2. 02
    Marks what will break

    On the exact file and line

  3. 03
    Hands your agent the fix

    Then checks again

posts-app · launch review01 / 03
supabase/migrations/0001_posts.sql
1create table public.posts (
2 id uuid primary key,
3 user_id uuid,
4 body text
5);
6alter table posts enable row level security;
7create policy "owner" on posts
8 using (auth.uid() = user_id);

no RLS: check roles and grants

re-checked · 75 → 95

Agent hand-off File · line · next step Review
the prompt
Run the checks again
Hand-off

Your agent gets
a focused prompt

  • Claude Code, Codex and Gemini CLI
  • The prompt names the file and line
  • Re-checks before it calls it fixed
Findings

Every finding, redlined

Run it before
your users do

Run the check $ npx -y viberavencopied
Example checklistposts-app
  • No blockers in the code
  • Row level security on every table
  • Stripe webhook signature checked
  • Env vars set in production
  • Error monitoring wired in
Example