Farol-style PR risk brief for approvers

A risk map and review checklist for the person approving a pull request

Problem

Code review pain falls hardest on approvers: PRs are getting bigger and increasingly AI-generated, so the few risky lines drown in formatting and boilerplate. Approvers skim by gut feel, and when something breaks they own the blame. Existing tools comment in CI but rarely organize information for the reviewer personally.

Solution

Analyze the PR diff and surrounding context, flag high-risk areas (dependency changes, missing error handling, config/permission edits, cross-module calls), and produce a one-page approval map: what must be read closely, what can be skipped, and likely behavioral impact. Ships as a GitHub App or CLI with a shareable summary page.

Users

Tech leads at small teams, senior engineers doing review as a side duty, open-source maintainers

MVP

GitHub App that reads PR diffs and scores them with rules plus an LLM; risk-ordered review checklist; one-click summary comment on the PR; ignore rules by path or file type; audit log of risk points the approver confirmed

Revenue

Per-repo subscription (one private repo free), team plan per seat; free for public repos to drive word of mouth

Why now

AI coding has exploded PR volume and size, making human review the bottleneck; LLM diff explanation is now cheap enough for an indie to run