Dev
Code Review Comment Generator
The way a review comment is phrased shapes how it lands. A blunt directive can feel like a command, while a question invites collaboration. This generator produces review comment templates phrased as suggestions, grouped by the concern you are raising. One input controls the output: the Focus dropdown — Readability, Performance, Naming, Tests, or Error handling. For each focus, four templates are returned in a shuffled order. Readability covers function size and nesting. Performance covers loop hoisting and N+1 queries. Naming addresses vague names and abbreviations. Tests prompts for edge-case and error-path coverage. Error handling covers uncaught failures and silent swallowing. Treat these as sentence starters. Anchor every comment to a specific line and add the reason why it matters — that turns the template into actionable feedback.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Pick the focus of your review feedback.
- Click Generate to see suggestion templates.
- Pick the phrasing that fits the situation.
- Tie it to the specific line and explain the why.
Use Cases
- •Phrasing review feedback constructively
- •Finding kinder wording for a harsh comment
- •Remembering which angles to check in a review
- •Keeping review tone consistent across a team
- •Teaching new reviewers how to give good feedback
Tips
- →Always anchor a comment to the specific code and the reason.
- →Ask questions where you are unsure rather than assert.
- →Praise good code too, not only problems.
- →Distinguish blocking issues from optional nits.
FAQ
what focus areas are available
Five: Readability (function size, intent clarity, nesting), Performance (loop hoisting, N+1 queries, allocation), Naming (vague names, inverted booleans, abbreviations), Tests (missing edge cases, test names, error paths), and Error handling (uncaught failures, silent errors, validation).
how many comments are returned per run
Four comments, drawn from a fixed pool of four templates per focus area, returned in a shuffled order. Each run may reorder them but always returns the same four for a given focus.
should I use the comments verbatim
No. Each comment is a generic template. Tie it to the specific line, add the concrete problem, and explain why it matters. A comment that says only "Suggestion: this name is a little vague" without a file reference or a better suggestion is unlikely to be acted on.
why phrase comments as suggestions rather than instructions
Questions and suggestions invite discussion and signal respect for the author's judgment. Directives can feel like criticism and cause friction. The collaborative framing makes it more likely the change will be accepted and keeps the review productive.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.