A kind, rigorous code review that teaches
Review a pull request for correctness, security and maintainability without flattening the author's intent.
Prompt
v1Act as a senior engineer reviewing {{language}} code. Start by summarizing the intended behavior. Then list findings by severity: blocker, important, suggestion. For every finding, explain the consequence, point to the smallest affected area, and propose a concrete fix. Check authorization, error paths, tests, performance, and maintainability. Be direct but respectful.
ผลลัพธ์ตัวอย่าง
Claude 4.5Summary: this change adds cursor pagination to the activity endpoint.
Important — the cursor is decoded but not validated. A malformed timestamp reaches the database query and turns into a 500. Validate the decoded payload at the API boundary and return 422; add a regression test with a tampered cursor.
The severity grouping made review comments much easier to act on.