llms.txt: machine-readable documentation index. Markdown version of this page is also available.

JetBrains Air Help

Review changes

After an agent implements a change, review the result before you open a pull request. Review is interactive: you can inspect diffs, navigate to modified files, comment on code, and turn feedback into the next iteration.

You review code that has already landed. Air Teams commits the agent's work to the task branch after every turn, so there is nothing to accept: each round of feedback adds a commit, until the branch is what you want – see What happens to your changes.

Review workflow

Review, iterate, and verify

  1. Open the task changes.

    Click a changed file in the chat, click Review Changes in the Task ready for review notification, or open the Changes tool. The merged diff opens in the editor in a single tab named All Changes, which lists every changed file with its added and deleted lines. Expand a file to read its diff.

    The All Changes tab listing the changed files with their paths and added and deleted line counts
  2. Navigate the diff and choose how to inspect it.

    Use the Diff View menu in the diff header to switch between Unified and Side-by-Side views. Use the arrows next to it, or F7 and Shift+F7, to jump to the next or previous change. You can also open the changed files and review them in the context of the whole project – see Explore code.

    The All Changes tab with the Diff View menu open, offering Unified and Side-by-Side
  3. Review the result and choose how to provide feedback.

    • Comment on code – add comments to specific lines and send them to the task as review feedback. See Comment on changes.

    • Add selected code to the task – send a selected code fragment directly to the task as context for a follow-up. See Add selected code to the task.

    • Have an agent review it – if the agent ships a review command or skill, such as /review, run it from the slash menu. See Commands.

  4. Iterate on the result.

    If more work is needed, send your review feedback to the task and let the agent update the result. You can also add more context using the same tools as when defining a task. Learn more in Task context.

  5. Verify the updated result.

    You can verify changes by running commands yourself in the Terminal tool, or by asking the agent to run commands or tests. For example, ask the agent to run newly added tests.

  6. When the branch is what you want, create a pull request.

Review actions

Comment on changes

Use comments when you want to leave review feedback on specific lines. Comments collect in the Comments tool, so you can review a whole diff and send your feedback in one go.

  1. In the diff or editor, select the code you want to comment on and click Add Comment.

  2. Enter your comment and click Add Comment.

    A comment field under line 61 of a file, with the comment text typed in and the Add Comment and Cancel buttons
  3. Repeat for every place you want to comment on.

  4. Open the Comments tool, keep the comments you want to send selected, and click Send.

    The comments go to the chat as a follow-up, and the agent answers them in the same task.

    The Comments tool with one selected comment on line 61 of Owner.java and the Send button

Add selected code to the task

Use this action when you want to send a selected code fragment directly to the task as follow-up input.

  1. In the diff or editor, select the code you want to reference.

  2. Click Add to Task.

    A selection in the editor with the Add to Task and Add Comment actions above it
  3. Enter the follow-up instruction and send it to the task.

06 November 2026