Code Review

Reviews against two things, not one: does it satisfy the spec, and is it well-designed regardless of the spec. A change can pass every acceptance criterion and still be bad code — call that out too.

Steps

1. Get the diff. gh pr diff <n> if there's a PR, or git diff / git diff main...HEAD otherwise.

2. Check against the spec. Open the linked docs/specs/<slug>.md and the specific ticket's claimed acceptance criteria. For each: does the diff actually satisfy it? Point to the specific lines, don't take the ticket's word for it.