What Types of Code Review Comments Do Developers Most Frequently Resolve?

📅 2025-10-06
📈 Citations: 0
Influential: 0
📄 PDF
🤖 AI Summary
This study investigates which types of code review comments developers are more likely to adopt, aiming to guide LLMs in generating high-adoption-rate review suggestions. We propose a five-dimensional taxonomy—readability, defects, maintainability, design, and style—and develop an LLM-as-a-Judge framework to automatically classify both human-written and LLM-generated review comments from real-world projects. Empirical analysis reveals that comments targeting readability, defects, and maintainability achieve significantly higher resolution rates; LLM-generated comments exhibit strong actionability overall and demonstrate complementary strengths relative to human reviewers across diverse project contexts. Our key contributions are: (1) the first systematic empirical characterization of the relationship between comment type and developer adoption behavior, and (2) validation of the LLM-as-a-Judge paradigm for code review quality assessment, demonstrating its effectiveness and generalizability across projects and comment categories.

Technology Category

Application Category

📝 Abstract
Large language model (LLM)-powered code review automation tools have been introduced to generate code review comments. However, not all generated comments will drive code changes. Understanding what types of generated review comments are likely to trigger code changes is crucial for identifying those that are actionable. In this paper, we set out to investigate (1) the types of review comments written by humans and LLMs, and (2) the types of generated comments that are most frequently resolved by developers. To do so, we developed an LLM-as-a-Judge to automatically classify review comments based on our own taxonomy of five categories. Our empirical study confirms that (1) the LLM reviewer and human reviewers exhibit distinct strengths and weaknesses depending on the project context, and (2) readability, bugs, and maintainability-related comments had higher resolution rates than those focused on code design. These results suggest that a substantial proportion of LLM-generated comments are actionable and can be resolved by developers. Our work highlights the complementarity between LLM and human reviewers and offers suggestions to improve the practical effectiveness of LLM-powered code review tools.
Problem

Research questions and friction points this paper is trying to address.

Identifying which LLM-generated code review comments developers most frequently resolve
Comparing comment types from human reviewers versus LLM-powered tools
Analyzing resolution rates across five categories of review comments
Innovation

Methods, ideas, or system contributions that make the work stand out.

LLM-as-a-Judge classifies review comments automatically
Taxonomy categorizes comments into five distinct types
Identifies high-resolution comment types for actionable feedback
S
Saul Goldman
The University of Melbourne, Australia
H
Hong Yi Lin
The University of Melbourne, Australia
Jirat Pasuksmit
Jirat Pasuksmit
Atlassian
Software EngineeringAgileEffort Estimation
P
Patanamon Thongtanunam
The University of Melbourne, Australia
K
Kla Tantithamthavorn
Monash University, Australia
Z
Zhe Wang
Atlassian, Australia
R
Ray Zhang
Atlassian, Australia
A
Ali Behnaz
Atlassian, Australia
F
Fan Jiang
Atlassian, Australia
M
Michael Siers
Atlassian, Australia
Ryan Jiang
Ryan Jiang
University of Waterloo
machine learning
M
Mike Buller
Atlassian, Australia
M
Minwoo Jeong
Atlassian, USA
M
Ming Wu
Atlassian, USA