Coding and Data
Include the ticket or acceptance criteria. Without them, the review tends to drift into generic style advice.
Review this change against the stated requirements. Report only issues introduced or exposed by the patch. For each issue, give severity, exact file and line, the failure scenario, and the smallest safe correction. Do not report style preferences unless they cause a defect. Requirements: [REQUIREMENTS]. Patch: [DIFF]. Relevant tests: [TESTS].REQUIREMENTSDIFFTESTSA prioritized defect list tied to evidence in the patch, followed by any missing test coverage.
AI output can be incomplete or wrong. Verify facts, run code, check citations and keep private data out of tools that your organization has not approved.
Subscribe now to keep reading and get access to the full archive.