From 885187a1af3a21359e0f143c8d075283a56d5cbf Mon Sep 17 00:00:00 2001 From: Joel Lamy-Poirier Date: Fri, 1 May 2026 03:02:05 -0400 Subject: [PATCH] Number review items for easy reference Reviewers should number every item so the user can respond by number ("fix 2 and 4", "ignore 5") rather than re-quoting text. Belongs in the PR review focus section alongside the other discipline bullets. Co-Authored-By: Claude Opus 4.7 (1M context) --- CLAUDE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CLAUDE.md b/CLAUDE.md index fb4bb712c..265b017cb 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -188,3 +188,4 @@ When reviewing PRs (`/review` reads this section as part of its checklist): - **Correctness**: edge cases, off-by-ones, error handling, race conditions. Read the code; don't trust comments. - **Test coverage**: new code paths should have tests; modified behavior should have updated tests. Untested control flow is a flag. - **Diff discipline**: don't substitute commit messages or `git --stat` for reading the code. On a follow-up review after fixes, read `git diff ..HEAD` in full before claiming an item is "verified" or "fixed". Never put ✅ on items whose diff you haven't read. +- **Numbering**: number every review item (1, 2, 3...) so the user can reference them by number when responding (`fix 2 and 4`, `ignore 5`). Don't use unnumbered bullets where ordinals would make items addressable.