Outline: (1) why code review; (2) architecture of the workflow; (3) secret + workflow file; (4) the review script; (5) testing with a deliberate issue; (6) extensions and other AI-in-pipeline patterns.
Ask which review comments they write over and over. Those are the candidates for automation.
The page draws the same loop as a step-by-step diagram under the design decisions; the simulator's "large PR" plays it.
False positive: a fake secret in a test resource. False negative: the issue sits after the 3 000-line cut. The job fails: no ANTHROPIC_API_KEY secret, or the API stays overloaded (529). The page has the same table with markers.
Embedded twice: at the end of section 4 (opening on 4 · 5.1) and under the 5.4 table (opening on 5.4 gate).