Quickstart

By Ohad Krispin, founder of VibeRaven · LinkedIn

Run one command in your project root and VibeRaven lists what to fix before launch, each with a file and a line. It takes about a minute, needs only Node.js, and nothing leaves your computer.

npx -y viberaven@1.7.8 check

Use npx.cmd in Windows PowerShell if npx is blocked by the execution policy. Or ask your coding agent to "run npx -y viberaven@1.7.8 check and fix what it reports".

Before you start

Node.js 20 or newer. Check with node -v.
Your app folder, ideally a git repository. No account, API key or provider access is needed.

Run the check

Open a terminal in the project root, the folder with package.json.
Run the check. To check another folder, pass its path at the end.
```
npx -y viberaven@1.7.8 check
```
Read the verdict on the last lines, then the findings above it, most severe first.

Read the result

Each finding is a title, its id in brackets, the file and line, and what it found. This is part of a real run on a fixture repo:

viberaven check · ./my-app

🔴 No RLS policy proof in migrations  (rls_disabled)
   supabase/migrations/20260101000000_init.sql:1
   2 public tables without row level security: public.profiles (supabase/migrations/20260101000000_init.sql:1), public.invoices (supabase/migrations/20261102000000_invoices.sql:1). ...
   Guide: https://viberaven.dev/find-supabase-tables-missing-rls
🟡 Supabase connection is not using the pooler port  (pooler_port_mismatch)
   .env.example:13
   Found direct 5432 DATABASE_URL/POSTGRES_URL evidence. Vercel/serverless deployments should prefer Supabase transaction pooler port 6543.

Verdict: ❌ 9 blockers, 11 warnings · score 5
Fix: viberaven fix · Details: ./my-app/.viberaven/agent-tasklist.md

What each mark means
Mark	Severity	Meaning
🔴	Blocker	Fix before launch. `check` exits 1 when there is at least one.
🟡	Warning	Worth fixing; it does not change the exit code.
⚪	Info	Context, such as a table locked to the service role.

Every id is explained in the findings reference. A repo with nothing to report prints ✅ No launch blockers found in repo evidence.

Fix one finding

Some findings have an automatic fix. List them, write a plan for one, then apply it. Applying needs no confirmation, so read the plan first.

npx -y viberaven@1.7.8 fix
npx -y viberaven@1.7.8 fix --gap missing_error_boundary --dry-run
npx -y viberaven@1.7.8 fix --gap missing_error_boundary

For the rest, hand the finding to your coding agent. prompt --gap <id> prints a focused prompt for one finding. Then run the check once more to confirm it is gone.

What it writes

The check writes its results to .viberaven/ in the project: agent-tasklist.md for your agent, gate-result.json for the verdict and last-scan.json. It does not change your code. Add .viberaven/ to .gitignore if you do not want to commit it.

Checked

Checked on November 3, 2026, against the published viberaven 1.7.8, with a real run on a small Next.js + Supabase + Stripe fixture repo.