GitHub PR Review

Connect every PR to the product context it implements.

OAuth + webhooks + AI code critique with spec alignment.

REVETOOL syncs your GitHub PRs and links them to the screens and tickets they implement. AI reads the diff, the linked specs and the original Figma frame to surface gaps between intent and reality.

How it works

A clean workflow your team can adopt today.

1

Connect GitHub via OAuth

Workspace-level GitHub OAuth + per-project webhook with HMAC signature verification. Tokens encrypted server-side.

2

Auto-link PRs to screens and tickets

Webhook on PR open: REVETOOL extracts [US-XX] from title, links to the right ticket, auto-creates staging screen for the preview deployment.

3

Review with AI code context

When analyzing a screen, REVETOOL AI fetches the top related files from GitHub (heuristic naming match) and includes them in the prompt context.

Capabilities

Built for the moments your team actually needs it.

01

GitHub OAuth + webhooks

Per-project webhook with HMAC verify. 1 secret per project. Pre-launch tested end-to-end on real repo.

02

PR cache sync

PRs cached locally with check-runs aggregation. Refresh on demand or auto on webhook. UPSERT idempotent.

03

Auto staging screens

PR opened → screens auto-created with env_kind=staging + label 'PR #N' + auto-link to the linked ticket via M2M.

04

AI code context (top 3 files)

Heuristic naming match: extract keywords from screen path → score files → truncate 200 lines / 5KB → inject in prompt.

Why it matters

What changes for your team.

  • Devs stop explaining what a PR implements — REVETOOL shows it
  • PMs see PR status next to the ticket and screens they affect
  • AI catches misalignment between spec and code before code review
  • QA can scope tests to the screens that actually changed

See it on your real product.

Book a 30-minute demo and we will run REVETOOL on your stack.