{"version":"2.1.239","anchor":"code-review-findings-now-carry-a-short-summary-and-a-categor","canonical_anchor":"code-review-findings-now-carry-a-short-summary-and-a-categor","heading":"Code review findings now carry a short summary and a category","tier":"notice","area":"Code Review","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/code-review-findings-now-carry-a-short-summary-and-a-categor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Code review findings now carry a short summary and a category\n\nCode review findings now carry a short claim and a category like correctness or efficiency.\n\n**What**\n\nEach finding in a code review must now include a one-line claim of at most 60 characters with no rationale, plus a category slug such as correctness, simplification, efficiency, reuse, altitude or conventions, alongside the existing file, line, summary and failure scenario.\n\n**Details**\n\n- The review is also forbidden from printing the same findings as plain text or publishing them as a separate artifact.\n\n**Evidence**\n\n`the claim compressed to \u226460 characters, no rationale`\n\n- Area: Code Review\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}