Helix Core is now P4 and Helix Swarm is now P4 Code Review. Product user interfaces will be updated soon. Learn more >>

Documentation | 2025.4

# Contribute comments or code changes to a code review

You can contribute to a code review in the following ways:

- Comment on a review
- Comment on a review description
- Comment on a specific line in a file
- Comment on a file in a review
- Reply to a comment
- Edit files in a review

## Comments

Comments are the primary feedback mechanism provided by P4 Code Review. Review comments can be flagged as tasks for a lightweight workflow within a review that helps authors and reviewers prioritize review feedback.

Use the AI Assistant to review and improve the text in a comment before you post it. The AI Assistant can return a summarized version of the text, fix the spelling or grammar, or return a generated response for custom prompt. For information on setting up a custom prompt, see AI Assistant for comments.

By default, comment notifications are delayed to allow you to add or edit comments as you progress through a review without sending a notification for each individual comment on the review. Comment notifications are rolled up into a single notification that you can either leave to be sent automatically, or you can send manually, see Comment notification delay.

For more information about comments and comment features, see Comments.

### Comment on a review

1. From the review page: click Comments to view the Comments tab.
2. Add your comment in the text area.
3. Optional: select the Flag as Task checkbox to mark the comment as a task that needs to be addressed.
4. Click Post.

### Comment on a review description

1. From the review page description area: click Comments (n) (where n is the number of comments that already exist).
2. Click Add a comment.
3. Add your comment in the text area.
4. Optional: select the Flag as Task checkbox to mark the comment as a task that needs to be addressed.
5. Click Post.

To hide the description comments, click Comments n (where n is the number of description comments that exist). To display the comments again, click Comments n.

### Comment on a specific line in a file

1. From the review page: click Files to view the Files tab.
2. Click on the line you want to comment on.
3. Add your comment in the text area.
4. Optional: select the Flag as Task checkbox to mark the comment as a task that needs to be addressed.
5. Click Post.

### Comment on a file in a review

1. From the review page: click Files to view the Files tab.
2. If there are multiple files, click the file you want to comment on to expand its view.
3. Click the Add a Comment link in the footer of the file display.
4. Add your comment in the text area.
5. Optional: select the Flag as Task checkbox to mark the comment as a task that needs to be addressed.
6. Click Post.

### Reply to a comment

1. From the review page: click Comments to view the Comments tab.
2. Navigate to the comment you are replying to.
3. Click Reply below the comment you are replying to.
4. Add your comment in the text area.
5. Optional: select the Flag as Task checkbox to mark your reply as a task that needs to be addressed.
6. Click Post.

## Editing review files

### Edit files in a review

1. Get a local copy of the review's files.

2. Edit the files as required.

3. Prepare a changelist with the edited files and include `#review-1234` within the changelist's description (separated from other text with whitespace, or on a separate line), where `1234` is the review's identifier.

   If you use an invalid review identifier, it will appear that nothing happens. P4 Code Review is currently unable to notify you of this situation. If the review has not been correctly updated, use the Add Change button in the review heading to add the changelist to the review, see Add a changelist to a review.

4. Depending on the model of code review you are using, you would:

   - Shelve the files (for pre-commit).
   - Submit the files (for post-commit).

Your search for returned results