code-review

To get structured code review feedback on a pull request, submit your code changes and request a review. The process categorizes findings into strengths, concerns, and concrete suggestions to enforce quality and readability.

Reviewing a diff for correctness and readability involves applying a best-practice checklist that assesses adherence to standards. It yields categorized findings, highlighting short-term fixes, long-term design improvements, and missing tests.

Yes, you can use this code review checklist across different programming languages. It applies to patch sets and diffs regardless of language, guiding reviewers to evaluate safety, clarity, and coverage consistently.

To ensure code review feedback includes prompts for missing tests and docs, use a structured review process that explicitly checks coverage. It categorizes output into strengths, risks, and suggestions while flagging omitted documentation.

A high-quality code review feedback report should look like a structured output separated into strengths, concerns, and suggestions. It provides actionable feedback guiding both immediate fixes and long-term design improvements.