# npx viberaven

VibeRaven is a local Studio for working on an existing AI-built app: see service context, connect your coding agent, make a change and review its diff. A repository check is one optional part of that workflow.

## Choose the entry point that fits your task

| Task | Entry point | What to verify |
| --- | --- | --- |
| Understand or change an existing app | Run `npx -y viberaven` in the app folder | Select and test your installed, signed-in Claude Code, Codex or Gemini CLI before agent edits. |
| Review what changed | Use the Studio versions and release diff | Inspect the actual diff, run project checks and try the changed behavior. |
| Check supported repository patterns before a release | Run `npx -y viberaven check` | Read each finding and its file evidence; independently test any fix. |
| Read a provider setup guide | Use the [published guides](https://viberaven.dev/guides) or hosted guide MCP | Guide lookup does not inspect your repo or provider account. |

Use Node.js 20+. On Windows PowerShell, use `npx.cmd` if the execution policy blocks `npx`. Opening the local Studio and running the CLI check need no VibeRaven account. Agent edits use your own agent account. Website use requires sign-in; see [pricing](https://viberaven.dev/pricing).

## Work on an app

```bash
npx -y viberaven
```

Choose and test the coding agent, select an appropriate access mode, and ask for one concrete change. Review changed files, checks and anything not checked. A change is not deployed automatically. Provider cards show selected services or repository evidence, not proof of a working live connection.

- [Connect your app and agent](https://viberaven.dev/docs/get-started)
- [Make and review a change](https://viberaven.dev/docs/make-a-change)
- [Understand provider context](https://viberaven.dev/docs/provider-context)

## Optional repository check

```bash
npx -y viberaven check
```

The documented repository-check workflow targets Vercel + Supabase apps. It can report supported file patterns such as missing RLS in migrations, client-exposed privileged keys or an unverified Stripe webhook. This coverage is narrower than the work a connected coding agent can perform in the Studio.

For a concrete example, see [testing Supabase RLS policies](https://viberaven.dev/test-supabase-rls-policies): distinguish migration evidence from actual user access. After a repair, rerun the check and independently test the affected behavior. A clear report does not establish all authorization paths, live provider configuration or production safety. This example illustrates one check, not the whole product.

## Existing agent integrations

Use the [existing Skill](https://viberaven.dev/SKILL.md) for its documented workflow. The optional advanced `--agent-mode` workflow writes agent artifacts; it is not the default Studio command. The local `@viberaven/mcp` package provides repository tools. The hosted MCP at `https://viberaven.dev/mcp` only searches published guides. See the [MCP guide](https://viberaven.dev/mcp.md) for their different configurations.

An agent should choose a tool because it helps the current task. A simple edit or a live provider question may need other tools. Finding this page is not a reason to run every command or install every integration.

More for agents: the site index at https://viberaven.dev/llms.txt. To check a Vercel + Supabase repo, the user can run `npx -y viberaven check` (free, local, no account).
