code-review

@akillness

Turn a PR, diff, merge request, or patch stack into one evidence-first review brief. Use when the main job is deciding approve vs request-changes vs block, naming the highest-risk findings, calling out missing proof for risky paths, and routing Git cleanup, debugging, test-policy, visual-review, or repo-admin work to the right neighboring skill instead of absorbing it.