VibeRaven

Install rules for your coding agent

By Ohad Krispin, founder of VibeRaven · LinkedIn

`init` writes a short VibeRaven block into the instruction files your coding agents read, so they run the check when they touch migrations, auth, webhooks, env vars or deploy config. It edits files in your repo, so preview it first with `--dry-run`.

npx -y viberaven@1.7.8 init --dry-run

The dry run lists every file it would write, prints the block, and changes nothing. Or ask your coding agent to "install the viberaven rules in this repo".

Install

  1. Preview what init would write.
    npx -y viberaven@1.7.8 init --dry-run
  2. Write it. With no flags, init writes every target below.
    npx -y viberaven@1.7.8 init
  3. Review the diff and commit the files you want to keep. No account is needed.

What it writes

In the agent files, the block sits between <!-- VIBERAVEN:START --> and <!-- VIBERAVEN:END -->. Text outside the markers is left alone.

Files init writes in viberaven 1.7.8
AgentFiles
CodexAGENTS.md and the Skill in .agents/skills/viberaven/SKILL.md
Claude CodeCLAUDE.md and the Skill in .claude/skills/viberaven/SKILL.md
Gemini CLIGEMINI.md
CursorFour rules in .cursor/rules/: viberaven-core.mdc, viberaven-supabase-rls.mdc, viberaven-deploy.mdc, viberaven-payments.mdc
GitHub Copilot.github/copilot-instructions.md
Every agent.viberaven/agent-rules.md, agent-context.md, mission-map.md and task-contract.template.json

The full text it installs is published at agent-rules.md.

What the rules say

When the agent changes or reviews Supabase migrations or RLS, auth, Stripe webhooks, env vars or deploy config, the block tells it to:

  1. Run npx -y viberaven check from the repository root.
  2. Fix the repo-code blockers it lists, and ask you before a fix that needs your yes, such as enabling RLS on a table with no policies.
  3. Run the check once more after the batch, not after every edit.
  4. Report the provider steps it could not see, and not call the app production-ready or secure because the check is clean.

It also says that the check is advice, not a gate, and that the agent never signs in or pays for you.

Pick agents

Pass a comma-separated list to --agents to write only some targets.

npx -y viberaven@1.7.8 init --agents claude,codex --dry-run

Valid targets: all, codex, claude, cursor, cursor-legacy, copilot, github-copilot, gemini, agent-context, mission-map, agent-rules, claude-skill, codex-skill, devin, windsurf, cline, roo, junie and zed.

all covers the files in the table above. Name devin, windsurf, cline, roo, junie, zed or cursor-legacy to add those too.

Check in CI instead

init --github writes GitHub Actions workflows that check every pull request. See CI.

Next

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.

All VibeRaven docs