Every pull request,
reviewed before
it becomes a problem.
Gitvora reads every diff the moment it lands — bugs, security holes, missing tests, risk score — and posts the verdict before a human reviewer even opens the tab. Runs on your own hardware, or ours.
One reviewer, six jobs it never skips.
Every review type ships with its own prompt, its own output schema, and its own escalation rule.
Standard review
Runs on every PR open and update. Bugs, performance, and style — scoped strictly to what's in the diff.
automaticDeep review
Full files, not just diffs. Cross-file impact and architecture-pattern checks for the PRs that deserve a slower, harder look.
@gitvora deep reviewSecurity scan
Injection, auth gaps, hardcoded secrets, SSRF, XSS — checked against a fixed checklist. Always cloud-tier.
@gitvora securityExplain
Plain-English summary of what a PR does and why it matters, calibrated to junior, senior, or non-technical readers.
@gitvora explainRisk score
A weighted 0–10 score from lines changed, file sensitivity, security findings, coverage delta, and complexity.
automaticTest coverage
Finds the functions nobody tested and writes the missing test in your existing framework's actual style.
@gitvora test coverageRuns on whatever you've already got.
CPU-only, GPU-only, or a hybrid mix — auto-detected on startup, with a manual override if you'd rather decide yourself.
Cloud only
No local hardware needed. Every review routes straight to the cloud model.
CPU-only
Quantized 3B–7B models on commodity hardware. Fast first-pass review, cloud only when it has to escalate.
CPU + GPU hybrid
Partial GPU offload sized to your actual VRAM. The sweet spot between local speed and model quality.
GPU-only
Full model offload to a dedicated GPU. Local speed at near-cloud review depth.
It only spends cloud money when the diff earns it.
Small, ordinary changes stay on your own hardware. Anything touching payments, auth, or secrets escalates automatically.
Configure it like infrastructure, not a black box.
Routing rules, channel bindings, hardware overrides, and prompt behavior — all editable, versioned, and rollback-able from one screen.
| Pull request | Repo | Risk | Verdict |
|---|---|---|---|
| #412 Refactor checkout flow | storefront | 6.8 | warnings |
| #409 Add retry to webhook handler | payments-api | 2.1 | pass |
| #405 New invoice export job | billing | 8.9 | blocked |
Pay for the model you actually need.
Four deployment modes, same six review types. Move between them as your team or your hardware changes.
Cloud only
Simplest setup. Every review on the frontier model, billed per use.
Mostly local
CPU-only hardware handles routine reviews; cloud only for escalations.
CPU-only, full local
Lowest cost ceiling. Best for teams who can tolerate the fast-model tradeoffs.
GPU / hybrid
Local speed close to cloud quality. The mode most teams land on.
Put a reviewer on every repo that needs one.
Free to self-host on your own hardware. No credit card for local-only mode.