Docs
Documentation
Everything you need to install Revvu, understand how reviews work, tune the bot to your team, and know what Revvu does with your code.
01
Install the GitHub App
Sign in with GitHub from the homepage and pick the repositories you want reviewed. One click, no config.
02
Open a pull request
Revvu receives the webhook, queues the review, and posts inline comments — usually under a minute.
03
Push fixes, get a new pass
Every push re-reviews only what changed. Fixed comments are auto-resolved.
New to Revvu? Start with the getting-started guide. Already installed and want to tune the bot? Jump to configuration.
Walkthroughs
Learn by doing
Journey-style guides that walk you through Revvu from your first install to tuning it to your team.
Getting started
Sign in, install the GitHub App, and watch your first pull request get reviewed in about five minutes.
ReadHow it works
The two-stage review pipeline — fast summary in about 10 seconds, deep review in under a minute.
ReadMentions and on-demand commands
Talk to the bot in PR comments — ask questions, teach it conventions, or trigger a fresh review.
ReadInline review comments
What's inside each comment — severity, category, evidence, and team-memory attribution.
ReadThe dashboard
A tour of the dashboard — overview metrics, repo settings, review history, and learnings.
ReadReference
Settings, security, and FAQs
Look-up pages for every config knob, the security model, and the questions other teams ask.
Configuration
Every per-repo setting — what it does, the default, and when to change it.
ReadTriggers
When reviews fire — PR open, new commits, mentions, draft transitions, branch filters.
ReadFix detection and dedup
How the bot stays quiet on follow-up pushes — recognising fixes, suppressing duplicates, auto-resolving threads.
ReadTeam memory and learnings
Teach the bot your conventions by replying to comments — and review what it has learned.
ReadSecurity model
What the bot accesses, what it stores, and how every webhook is verified.
ReadFrequently asked questions
Common questions about Revvu — answered.
ReadSeverity levels
How Revvu tags each comment
Every review comment gets one of four severity labels. Use them to triage at a glance.
A real bug or security risk. Shipping this will break production or expose users. Act before merge.
Likely-wrong behavior or risky pattern. Review carefully — probably worth fixing before merge.
A concrete improvement that would make the code clearer, faster, or safer. Optional but recommended.
Style or taste. Take it or leave it — Revvu won't block on these.
Want the full anatomy of a review comment? Read the inline comments guide.
All pages