io.github.ohad6k/viberaven

Plan setup and integration before implementing a feature that touches a provider. Returns versioned setup guidance, gotchas, dated changes, integration seams, existing repo checks and planned live checks with official sources. Available packs: supabase. Limits: guidance only; does not connect to providers, read your project, run checks or verify that a feature works.

Read the current chat-native action surface from .viberaven/actions.json. Use this to list stable, referenceable action IDs the user can verify or refer to by name.

Run local Vercel + Supabase production checks: table RLS presence, policy quality, view/function boundaries, service-role boundaries, and Vercel pooler usage. Call this when the project uses Supabase or Vercel and you need a focused infra audit beyond the general readiness check. Pass json: true for machine-readable output.

Useful before an AI-built app on Vercel and Supabase launches or is handed off. Runs the local `viberaven check` (no login, no API key, no telemetry), which reads the repository for launch gaps (missing RLS in migrations, leaked secrets, unbounded queries, unsigned webhooks) and writes a prioritized task list to .viberaven/agent-tasklist.md plus a verdict to .viberaven/gate-result.json. This is advice, not a gate: the user decides when to ship. It reads repo files and does not query the live database.

Write a non-destructive cleanup plan for generated .viberaven artifacts and logs. Call this when the .viberaven directory has grown stale. Does not delete anything; it only produces a reviewable plan.

Refresh and return .viberaven/context-map.json, a compact summary of the last scan for the next agent step. Use this to load minimal context before acting on a gap.

Run a fresh local scan (`viberaven --json`) and return the verdict it writes to .viberaven/gate-result.json (gate.status is clear, warning or not_clear). It rewrites the .viberaven artifacts; it does not read an older result without scanning.

Apply a guarded repo-code heal recipe for a supported gap. Only call this after viberaven_heal_plan. Pass yes: true to skip confirmation. The rls_disabled recipe writes a migration that enables row level security with no policies, so browser reads of those tables return no rows until policies exist: call it only after the user agrees. Its task leaves out yes: true; pass yes: true only once the user agrees. Returns the applied change summary, with any warnings.

Write a non-destructive heal plan (.viberaven/heal-plan.md) for a specific gap or target file, to review before viberaven_heal_apply. The plan names the target and the verify command. For rls_disabled it also shows the new migration it would write and its SQL, or why it will not write one; other gaps get no patch preview. Does not modify source files.

Return an agent-ready prompt that fixes a specific gap. Use this when you want a coding agent to apply the fix itself rather than using the guarded recipe.

Install bounded VibeRaven agent-instruction rules into native AI instruction files (CLAUDE.md / AGENTS.md / .cursor/rules), so coding agents know when a VibeRaven pass applies. Use dryRun: true to preview first.

Local candidate feature: disconnect the saved live step and remove its locally retained provider credential and evidence. Does not alter provider settings or unrelated MCP credentials. Unfinished account reservations expire. Local checks stay free.

Local candidate feature: resume the SAME saved live step through account connection, allowance and metadata verification. Set approvedRead=true only after the person explicitly approves the named Supabase project/schema catalog read. Show any returned action URL and wait for the person; never approve sign-in or payment for them. Credentials stay local and are never tool arguments. Vercel stays blocked; local checks stay free.

Local candidate feature: save a scoped metadata-verification request without provider reads or payment. Supabase catalog reads require a VibeRaven account and explicit human consent on resume. Vercel is deliberately blocked before network access. Local repository checks stay free without an account. Never pass credentials as tool arguments.

Local candidate feature: read the saved live-step receipt without provider reads, payment or another live-step charge. Evidence is historical and scoped, not proof of application security. Local checks stay free.

After reviewing a Supabase migration or ownership policy, optionally execute already reviewed local permissions scenarios for owner, other_user and anon. Returns Pass, Fail or Unknown per cell with the original scoped evidence. This is an experimental PGlite imitation, not live Supabase proof. The optional PGlite dependency must already be installed next to the matching CLI used by this local MCP host; missing setup returns the CLI setup guidance as a tool error. No SQL, credentials, provider calls or dependency installation are accepted.

Run `viberaven --strict --json` and return the verdict from .viberaven/gate-result.json (gate.status is clear, warning or not_clear). Useful before a deploy or CI run when the user wants the verdict as JSON. The user decides whether to ship.

Look up npm package names on the public registry (registry.npmjs.org). Returns not_found when the registry has no such package or cannot be reached, suspicious when the registry answers with an error other than 404, and suspicious when the package was first published less than 14 days ago and its name is within 2 character edits of a popular package (a typosquat signal), or when it has an empty description, no listed maintainers and 3 or fewer published versions. Anything else is ok, which only means none of these signals fired; it is not a security review of the package. Useful when an agent is about to add a dependency the project has not used before.

Re-run the local VibeRaven check after you apply fixes. Call this once per batch of fixes (not after every edit) to update .viberaven/gate-result.json and confirm whether the gate moved toward clear.

Verify or explain the lifecycle state of a stable VibeRaven action ID (format VR-A<number>). Use this when the user references a specific action and you need its current state.

Before implementing a local Node feature, freeze reviewed expected behavior and actual dirty/untracked baseline. Supports module comparisons, sequential HTTP requests to an isolated local server factory, and frozen Node preservation tests. No login or network; no commands or imported proof. MCP plans are limited to 4800 UTF-8 bytes; larger plans use the CLI JSON file (65536 bytes). No browser, database or live provider proof. Changed plans require a new task.

Export a bounded local draft proof report with Markdown from current integrity-checked verification receipts. Read-only: no login, network, Docker, agent or GitHub execution. Failed and unknown evidence remain explicit; agent success is not proof. Not authoritative CI or a completed live PR pilot. Review redacted text before sharing; redaction is not a complete secret scanner.

Resume the SAME saved task through account sign-in, quota or payment. Set approvedContract=true only after explicit human approval of its exact acceptance, must-not-break conditions and declared scope. A draft can be upgraded with contract before any job exists; its request must stay identical. Never authorize sign-in or payment for the person. Execution state is separate from independent verification observations; agent success is not condition proof. Scope declarations are not an enforced sandbox.

Save a versioned Task contract and run a free local check without login, network, edits or payment. Prefer contract; request alone saves a draft with unknown acceptance. No credentials or shell command fields. Review the returned contract before approving resume. Resume shares its short request and redacted results with the account; the full definition stays local. Provider and non-local contracts are planning only.

Read the saved Task contract, execution state and independent verification receipts locally without account, network, edits or payment. Current worktree changes invalidate checked proof; missing observations stay not_checked. Checked conditions separately report passed/failed outcomes. Historical agent results do not verify conditions.

Run or resume the SAME frozen plan using the locally available pinned Docker image only. Set approvedVerification=true only after human review/approval. Network is disabled and no dependencies are installed. No login or billing. Missing conditions, dependencies or Docker remain not_checked; completed receipts are reused for the identical candidate. Coding-agent success is not proof.