Think about the last time you merged a PR without a proper review.
Maybe tests passed. Maybe it looked fine at a glance. Maybe you were moving fast and told yourself you'd clean it up later.
Then two weeks later, a bug surfaces. Or a junior dev inherits the code and spends a day trying to understand it. Or a security scanner flags something in a production deploy.
"Looked fine" is not a review. It's a hope.
This is Part 2 of the copilot-workflow series. Part 1 covered setting up the template. This one covers using @code-reviewer — the staff engineer persona that reviews every change before it touches main.
