Back to Academy
Relevance 7/10Prompting and EvaluationAdvanced7 min read

Code Review Annotation

Code review annotation labels code quality issues such as bugs, style violations, and security concerns.

Why it matters for annotators

Detailed code labels improve model coding assistance quality.

Visual mental model

Code diff -> issue taxonomy -> annotated findings.

Examples (bad vs good)

Scenario: Real annotation scenario involving Code Review Annotation

Bad: Labeling quickly without applying project rubric.

Good: Applying rubric criteria, documenting rationale, and escalating uncertainty.

Common mistakes

  • Skipping guideline details for edge cases.
  • Applying inconsistent criteria across similar samples.
  • Avoiding escalation even when uncertain.

Submission checklist

  • Read the latest guideline update before each batch.
  • Apply rubric dimensions explicitly in each decision.
  • Escalate ambiguous items with concise rationale.