coming soonGitVim launches May 29, 2026 · 12:00 UTC— · — · — · —
coming · May 29, 2026 · 12:00 UTCbuilt onBase

Code review,
git-native.
vim-fast.

A GitHub App that drops real, actionable review on every PR — bugs, security flags, perf notes — then closes with a one-line verdict. $GITV on Base Base unlocks unlimited reviews and private repos.

/// launchesMay 29, 2026 · 12:00 UTC
days——
hours——
min——
sec——

// github app + dashboard go live · bookmark gitvim.cc

  • never blocks a merge
  • diff-only ingest
  • uninstall any time
  • idempotent per SHA
~/gitvim › PR #142 · feature/authLGTMNGMI

$gh pr open feature/auth

gitvim is reviewing… 2 files · 24 lines changed

@@ -42,9 +42,12 @@ async function getSession(req: Request) {
42 const cookie = req.headers.get("cookie")
43 const sid = parseCookie(cookie)?.sid
44 const session = sessions[sid]
44 const session = await db.session.findUnique({ where: { sid } })
45 return session.user
buggitvim · just now

No null check on `session` — throws on logout when the row is gone. Return `null` first.

46}
@@ -88,4 +91,7 @@ export async function search(q: string) {
91 return db.$queryRaw`SELECT * FROM posts WHERE title LIKE ${'%' + q + '%'}`
securitygitvim · just now

String-built SQL with user input — SQL injection. Use parameterized $1 or queryRawUnsafe with bound params.

92}
NGMI

/// 30 seconds

What actually happens on a PR.

Webhook → debounced queue → diff assembly → review engine → GitHub comment. No build steps in your repo, no Action to add.

~/gitvim › intro.mp4play
/// what it does

Real review,
on every PR.

GitVimreads your PR like a senior reviewer — works through the changed code, flags what's wrong, and tells you whether it's safe to ship. The persona is in the verdict; the review itself is plain, useful engineering feedback.

  • Reads only the diff

    Just the changed hunks — never the full repo. Generated, vendored, lock and binary files are skipped automatically.

  • Flags real issues, by severity

    Inline comments tied to the exact line, prefixed with [bug] [security] [perf] [error-handling] [readability].

  • Signs off with a verdict

    One blunt :LGTM or :NGMI verdict in the review summary, so reviewers know at a glance whether to merge.

gitvim bot · reviewed 2 files · just now

PR #142 · feature/auth · head 7c91a8e

NGMI
bugauth.ts:44

No null check on `session` — throws on logout when the row is gone.

securitysearch.ts:91

User input flows into the SQL query unescaped. SQLi.

perffeed.ts:13

N+1: fetching the author inside `map`. Batch with `whereIn`.

“two real bugs and one timebomb. fix these before this touches main.”

// posted as event: COMMENT · never a required check

/// how it works

Three commands. No config.

No required checks. No merge gates. Just a reviewer in your PR conversation, doing the work.

01install

Install on a repo

Add the GitHub App to a single repo, a folder, or a whole org. It only acts where it has access.

02open

Open a PR (or @mention)

On every PR — or when you say @gitvim — GitVim reads the diff and runs the review.

03review

Get the verdict

A summary, sharp inline comments, and a :LGTM or :NGMI verdict — posted as a normal review comment.

⌁ re-run any time with @gitvim on the PR

// pipeline · webhook → reviewack p50 < 80ms
PR opened
webhook · HMAC
queue
debounce · latest SHA
diff assembly
skip generated · cap
review engine
persona + rubric
GitHub review
COMMENT · never required
payload · diff hunks → tokens → review
posted · 1 summary + N inline
// one review per (repo, pr, head-sha)idempotent
/// the two verdicts

Two stamps. Same rubric.

Every review ends with one of two verdicts. Clean code ships. Broken code gets named, severity-tagged, and called out in plain English.

GitVim passes the PR
LGTMwhen it's clean

Short summary, no inline notes if there's nothing to flag, one-line verdict reason. Out of your way.

GitVim fails the PR
NGMIwhen it isn't

Severity-tagged inline comments on the lines that need work, plus a blunt one-liner telling you what to fix first.

/// 30-day findings

Every NGMI finding
carries a severity tag.

The same five tags show up in every review, in the same priority order. Reviewers skim by tag; authors fix by tag. No taste required.

severity / 30d
total · 1,290 findings
bug

No null check on `session` — throws on logout.

412
security

User input flows into the SQL query unescaped.

287
error-handling

Promise rejection swallowed in catch — failure goes silent.

261
perf

N+1: you fetch the author inside the map. Batch with `whereIn`.

188
readability

This 80-line function does three things — split it.

142
// across 2.3k reviewed PRsseverity = priority
/// token utility

$GITV unlocks more.

Hold $GITV on Base Base, get the better tier. No staking, no lockups, no funnels. Read-only balance check on every review.

/// compare

which tier fits?

Both tiers ship the same persona, rubric and verdicts. Holders get more headroom and the sharper model.

free

public repos

available May 29, 2026 · 12:00 UTC

best

holder

$gitv · base

available May 29, 2026 · 12:00 UTC

repo_visibility
Public only
Public + private
daily_rate_limit
10 reviews / repo
Unlimited
diff_size_cap
60 KB
400 KB
review_model
Claude Haiku 4.5
Claude Opus 4.7
reasoning_effort
default
high
on_chain_check
balanceOf · 60s cache

⌁ tier is resolved per-review · changes when your wallet balance does

/// guarantees

Won't be the bot you uninstall.

GitVim is designed to be the kind of reviewer maintainers actually want on their PRs. Every decision here keeps the noise down and the trust up.

guarantee

never_blocks

Posted as event: "COMMENT" — never becomes a required status check.

guarantee

no_noise

Generated, vendored, lock and binary files are skipped. Rapid pushes coalesce.

guarantee

easy_off

Uninstall the GitHub App any time. A .gitvim.yml disable flag is on the roadmap.

guarantee

diff_only

Only the changed hunks of the PR are sent to the model. No full-source crawl.

/// how the gate works

Token gate, in plain english.

On every PR, GitVimreads the PR author's linked wallet balance on Base and picks a tier. That's it. No staking, no escrow, no transactions besides one SIWE login.

network
Base mainnet
launch_venue
Clanker
check
Read-only balanceOf
cache
60 seconds per wallet
threshold
HOLDER_MIN_GITV (whole tokens)
never
Moves funds · asks for keys · writes on-chain
/// frequently doubted

Honest answers.

The short versions. Full nuance lives in the docs.

full docs →
~/gitvim › $ countdown launch.gitvcoming

$ launching

Launches May 29, 2026.

The GitHub App, the dashboard, and the $GITV gate go live on the same day. Bookmark gitvim.cc or grab the calendar invite — we'll be ready.

days——
hours——
min——
sec——

// May 29, 2026 · 12:00 UTC