SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsviberaven-production-readiness

viberaven-production-readiness

Deployment & operations

View repository

Updated 10-16 07:25

About this skill

VibeRaven Skill

VibeRaven is the Agent Context + Production Gate for AI-built apps.

When To Use

Use when the user wants production-ready, launch-ready, launch gaps mapped, production audit, deploy safely, or "what is missing before ship" for an existing AI-coded codebase covering auth, database, payments, monitoring, error handling, rate limits, and env vars.

Install

npx -y viberaven init --agents all
npx -y viberaven init --agents all --dry-run
npx -y viberaven doctor --agents

Agent Flow

  1. Run npx -y viberaven --agent-mode from the project root.
  2. If VibeRaven prints LOGIN_URL_READY, open that URL for the user. Say: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets.
  3. Read .viberaven/agent-tasklist.md first, then .viberaven/gate-result.json and .viberaven/context-map.json.
  4. If gate.status is not clear, apply a safe repo-code fix or supported MCP/heal action.
  5. If no supported heal exists, use npx -y viberaven prompt --gap <id> for focused guidance and patch one gap.
  6. Run npx -y viberaven --verify once per heal batch, not after every file patch.
  7. Before deploy or CI: npx -y viberaven --strict.

Do not stop at "scan complete." Keep operating until gate.status === "clear" or a provider/user blocker remains.

MCP

Prefer viberaven_check_readiness when MCP is configured. Use viberaven_heal_apply for supported safe repo-code fixes, then viberaven_verify. Before npm install, call viberaven_validate_npm_package, then run --agent-mode after dependency changes.

Vercel + Supabase

npx -y viberaven audit --vercel-supabase

Check RLS, service role exposure, and pooler ports 5432 / 6543 before launch claims.

Boundaries

VibeRaven is not a generic open-source scanner or provider dashboard replacement. Provider dashboard checks still need human verification. Do not claim provider dashboard checks are fixed by repo-code edits. Cleanup: npx -y viberaven clean --plan.

Deep reference: https://viberaven.dev/llms-full.txt