Place Review Comments

Time: 7 minutes. Tangible win: match each piece of feedback to the right comment target.

High-signal reviews put feedback where the author can act on it. `tuicr` supports line, range, file, and review-level comments, matching the same broad model used in pull request reviews.

Primary source GitHub's docs distinguish general PR feedback from line and file comments, and `tuicr` maps those ideas into terminal actions. See Commenting on a pull request.

Pick the smallest useful target

Feedback shape	Target	`tuicr` action
A specific line is wrong or unclear.	Line	`c`
A block works or fails as a unit.	Range	`v`, select, `c`
The concern is about the file overall.	File	`C`
The concern is about merge readiness.	Review	`<leader>c`

Avoid comment drift If a comment would force the author to hunt for the affected code, its target is probably too broad.

Retrieval check

You want to comment on a four-line block where the control flow breaks together. Which target fits best?

Correct. A range comment keeps the feedback attached to the whole block.

Not quite. Use a range comment when several adjacent lines form the issue.

Practice

Find one changed line and imagine a direct question for the author.
Find one changed block and decide whether a range comment is clearer.
Write one review-level summary sentence, even if you do not submit it.

Ask the agent to rewrite one of your review comments to be more specific and actionable.