What problem does it solve? Large pull requests are hard to understand from a diff alone, because hunks show what moved but never what the code decides. This Skill reads a PR's whole files and produces a compact model of the change so a reviewer can hold it in their head without sorting through findings. ## Core Features & Use Cases - Flow diagram: Builds a 10-15 node Mermaid diagram of the path through the system, marking what the change adds with NEW, and renders it to SVG via mermaid-cli. - Outcomes table: Lists one row per observable case, before and after, including unchanged cases and irreversible outcomes. - Reviewer map: Maps each reviewer question to the file that answers it, with a suggested reading order and production/test size counts. - Use Case: You are assigned a 40-file PR and cannot follow it from the diff. Run this Skill to get the flow, the observable behavior changes, and exactly which files to read in what order. ## Quick Start Ask the assistant to review PR #123 and produce the flow diagram, outcomes table, and reading map.
