Code Review Comment Writer
Write clear, constructive code review comments in seconds
gpt-4o-mini
Your prompt will appear here…
Your beautifully formatted article will appear here once you generate.
No history yet
Your generations will appear here. Sign in to save them permanently.
Have you ever typed a review comment, read it back, and deleted it because it sounded harsh? Or left the vague "maybe refactor this?" because the precise version would have taken ten minutes to phrase? Code Review Comment Writer turns your rough technical note into a comment that lands: specific about the problem, clear about how serious it is, and readable by the person who wrote the line.
Short answer: Code Review Comment Writer takes a rough note about a problem in someone's code and returns a posted ready review comment, with the tone, severity and format you choose, and an optional suggested fix.
What is Code Review Comment Writer?
Code Review Comment Writer is a free tool for the comment box in a pull request. You describe the issue as you would to yourself, for example "this loop re-queries the database on every iteration", and it writes the comment: what the problem is, why it matters, and what to do about it. The wording follows the tone and severity you pick, so a blocking security note and a friendly nit do not read the same.
Why A Blunt Comment Costs You A Day
Review comments carry more weight than their length suggests. A short, sharp line reads as criticism when the reader is tired, and the thread that follows costs you both an afternoon. A vague line is worse, because the author guesses at what you meant and pushes a change you did not ask for. The tool closes the gap between what you noticed and what you typed.
How Does Code Review Comment Writer Work?
- Write the raw observation in the prompt box, in whatever shorthand you use.
- Choose a model from the selector.
- Set Tone, Concern Type, Comment Format and Severity in the advanced options.
- Generate, read the comment, and copy it into the review thread.
The Output Length slider runs from Very Short to Comprehensive, and Very Short is the right default for a nit. Four toggles change what the comment includes: Suggest a code fix, Explain the why, Soften the wording and Link a best practice.
Tone, Severity And Concern Type
| Option | What it decides | Good starting value |
|---|---|---|
| Tone | How the comment sounds, from Constructive/friendly to Direct/concise, Mentoring or Formal | Mentoring for a junior colleague, Direct/concise for a peer |
| Concern Type | The angle, such as Bug/correctness, Performance, Security or Naming | Match it to what you actually saw |
| Comment Format | Single comment, Question/Socratic, Suggestion block, Nit prefix or Bulleted points | Suggestion block when you can propose the fix |
| Severity | Blocking, Should fix, Nit/optional, Praise or FYI | Set it honestly, because it sets the reader's reaction |
Severity is the setting people skip and should not. Marking a preference as Blocking is how review threads turn sour, and marking a real bug as a Nit is how it ships.
One Comment, From Rough Note To Posted
Say you paste: "getUserOrders runs a query inside the loop, N+1, this list can hit 500 rows". Set Concern Type to Performance, Severity to Should fix, Comment Format to Suggestion block and switch on Explain the why. The comment comes back naming the pattern, using the row count as the reason it matters, and proposing eager loading with a short code suggestion.
Pro tip Use the Praise severity now and then. A specific compliment on a clean abstraction takes one generation and does more for a review culture than three careful criticisms.
Habits That Keep A Review Moving
Worth doing
- Name the file and function in your note so the comment is concrete
- Keep one problem per comment
- Use Question/Socratic when you might be the one who is wrong
Worth avoiding
- Softening a genuine blocker until it reads as optional
- Posting a generated fix you have not read
- Pasting proprietary source when a description would do
Reviewing costs nothing on EizTools, with no login and no meter, and the model selector lets you try a different engine when a comment reads stiffly. Code Review Comment Writer keeps its own options panel, and you will find the rest of the developer tooling in the coding tools category. For feedback outside a pull request, the Peer Review Feedback Template covers the same care in a different setting.
Frequently Asked Questions
Do I have to paste the code itself?
No. A description of the problem is usually enough, and it keeps private source out of the prompt box. Paste a short snippet only when the exact lines matter.
Can it write the suggested fix?
Yes. Switch on Suggest a code fix and choose the Suggestion block format. Read the fix before posting it, because it is written from your description, not from your repository.
Will comments sound the same every time?
Change Tone and Comment Format between comments and they will not. Reviewers who leave every comment on identical settings are the ones who sound templated.
Is it useful for reviewing my own code?
Yes, and Code Review Comment Writer works well as a self check before you open a pull request, since it forces you to state the problem plainly.
Good review comments are not about being nice. They are about being understood the first time, so the thread ends in a commit instead of a debate. Drop your rough note in the box above, set the severity honestly, and post the version that says what you meant.
Sabir Bepari
Founder of EizTools and a passionate AI enthusiast dedicated to building practical, user-friendly AI tools that simplify everyday tasks.
Follow EizTools
New AI tools, practical tips and product updates — straight to your feed.
