Cookies, session recording and ad conversion measurement improve the product. Before you accept we measure page views and anonymous interactions, with no cookies, no recording and no profile. Reject keeps it that way. Cookie policy
Commit a VETOO.md to your repo root and Vetoo folds it into every review: calibrate severity, steer the voice, even ask for extras like a Mermaid diagram. Click a line to add it and watch the review respond. Tap a rule to toggle it and watch the review respond below.
Files changed 1
VETOO.md+1main
11# How to review this repo
vetoobotreviewed
Solid change overall. A few things worth tightening before this merges, mainly how the refresh-token query is built and what gets logged on the way through.
vetoobotblocking
Unparameterised query on the refresh token
vetoobotcomment
User email written to the request log
vetoobotcomment
No test covers the refresh path
vetoobotnit
Imports are not alphabetised
vetoobotadded a change summaryextra
Mermaid
vetoo holds the merge until 1 blocking item is resolved.
02It learns your team
Memory
Say it once. Vetoo keeps it.
Thumbs-down a finding and Vetoo suppresses that kind of comment in future reviews, per repo and per team. Vote below, then run the next review and watch what changes.
Review memoryPR #482 → #496
This review #482
vetoobotStyle · note
Prefer const over let for the unmutated config binding.
Teach vetoo
vetoobotSecurity · blocking
Raw user input flows into db.query(). Parameterise it.
Teach vetoo
vetoobotConvention · note
This file uses tabs; your change introduced spaces.
Teach vetoo
Vetoo’s memory of your team
Nothing taught yet. Use the vote buttons above.
Next review PR #496
Run the next review to see your feedback applied.
Vote on the left first to teach it something.
03While you sleep
Vetoo dreams
Human reviewers forget last week’s nitpick. Vetoo turns it into a rule overnight.
Overnight, the day’s scattered feedback gets pulled together: recurring signals connect into durable patterns, one-off noise drops away. Watch the map form, or step through it below.
Overnight consolidation Revisiting the day’s reviews
Today · the team’s signals
Tomorrow · Vetoo’s memory
Missing tests flagged on API routes×3
Tests expected on API routes
Security finding ranked first×2
Security findings prioritised
Tabs-vs-spaces nit voted down×2
Tabs vs spaces: muted
·One-off rename suggestion×1
Dropped, didn’t recur
What’s actually happening · step through it
04Your code is yours
Privacy by default
We review your code. We never keep it.
Vetoo only needs your code for as long as the review runs. It’s encrypted the whole way, handled in isolation, and gone the moment the verdict lands.
Encrypted
TLS 1.3Single-tenant isolationZero retentionNo model trainingBYOK supported
Every diff moves over TLS 1.3 and stays encrypted the entire time it’s in flight. Nothing ever travels, or sits, in the clear.
The honest ledger
What we keep
Pass / comment / block verdicts
Your up / down votes as review preferences
Suppression rules you set
Repo & pull-request identifiers
Metadata only. Enough to learn your team’s preferences, never your code.
What we never touch
Your source code
Secrets, tokens or env vars
File contents after the review
Anything used to train a model
None of this is stored, logged, or used to train anything. Ever.
Clear the review queue before it forms.
Connect your first repository and let Vetoo do the rest.
vetoobotreviewed