PR Blast Radius

Visual review panel mapping code changes to impacted user journeys

Problem

AI-assisted coding has exploded PR volume and review is increasingly automated, yet "which real user paths does this change touch" is still guessed by humans. Someone built a whole tool just to see a PR's blast radius, which shows the blind spot is widely felt.

Solution

Analyze the routes, components and APIs touched by a diff, combine that with existing integration tests or analytics mappings, and auto-generate a list of impacted user journeys as a PR comment. Configure the journey map once and reuse it continuously.

Users

Tech leads and platform engineers at mid-to-large frontend/full-stack teams, heavy users of AI-assisted coding

MVP

Parse PR diff and file structure; let users define a "file path to user journey" mapping table; generate impacted journey list as a PR comment; GitHub App install-and-go; a simple mapping editor

Revenue

Subscription per repo or per seat, listed on GitHub Marketplace; enterprise tier with a custom rules engine

Why now

AI-generated code is raising both PR count and review pressure, while user-journey-level review tooling is almost nonexistent, letting indie developers enter with lightweight mapping