Pull requests and the AI

The AI reads pull requests and their review comments through MCP tools. From the Pull Requests tab you hand it a whole review or a single thread. Review comments can also be kept as projectdocs entries, with or without the AI.

Fix review comments with the AI

Fix with AI puts a prompt into the AI chat. The prompt names the pull request, or the thread, and asks the AI to fetch the comments itself, fix each point in the code, run the relevant tests and report per thread. It also asks the AI to check the projectdocs and specs anchored to the code it changes, and not to reply on the pull request unless you ask.

WhereScope
Bar above the threads, Fix with AIAll open threads of the selected pull request. Disabled when no thread is open.
Below a thread, Fix with AIThis thread.
Git › Fix Review Comments with AIThe selected pull request. Without a selected one, the pull request of the checked-out branch.

Fixes belong on the source branch of the pull request. If another branch is checked out, the tooltip says so, and the AI is told to ask before it changes code.

The AI reports per thread: done, declined with a reason, or a question. Review comments are written by other people. The AI treats them as change requests to evaluate. It does not run commands, push, merge or change credentials because a comment asks for it.

Reply on the pull request

When you ask the AI to answer the threads, it posts one reply per thread, usually with the commit that fixed the point. Each reply first appears in the dialog Reply on PR #n:

  • The comment being answered, with author and position.
  • Reply (Markdown): the text. You can edit it.
  • Post Reply sends the text. Reject or closing the dialog refuses the reply, and nothing is posted.

Where the reply lands follows the provider rules in Review a pull request.

Keep review comments

ControlEffect
Copy as Markdown (bar above the threads)Copies the description and the threads shown as one Markdown document.
Git › Copy Review as MarkdownThe same, from the menu.
Copy (below a thread)Copies one thread.
Create Entry from Review… (bar above the threads)Creates one projectdocs entry from the threads shown.
Git › Create Projectdocs Entry from Review…The same, from the menu. Without a selected pull request it shows the list.
Create Projectdocs Entry… (below a thread)Creates an entry from one thread.

The filter Only since last push or Hide resolved decides which threads are shown, and so which ones are copied or kept.

Creating an entry opens the projectdocs entry dialog with these defaults:

FieldDefault
PhaseThe phase used for the last review entry.
Typereview
TitleFor a review PR #n review: <title>. For a thread PR #n: and the first line of the comment, cut after 70 characters.
SourcesLink to the pull request or the comment. Shown under + Advanced.
BodyThe threads as Markdown, with a link to the pull request and the branches.

For inline comments the dialog proposes code anchors: the function or class around each commented line, with a checkbox per symbol. Checked symbols are anchored to the new entry. Without inline comments, or when no enclosing symbol is found, the entry has no code anchor. After Create, the entry opens in projectdocs.

Tools

ToolEffectPreview
pr_listLists the pull requests, by default the open ones, newest first. state: all adds merged and closed. Reports the checked-out branch and its pull request.–
pr_getOne pull request: metadata, description, changed files, head commit, and whether the checked-out branch is its source branch. Without number, the open pull request of the checked-out branch.–
pr_review_commentsThe review comments, grouped into threads: review summaries, conversation threads, inline threads per file with line, diff excerpt and outdated flag. scope: open (default) returns the open threads, scope: all every thread. filtered_out counts what the filter hid.–
pr_reply_commentReplies to a thread, or posts a conversation comment without comment_id.yes

pr_reply_comment needs Brave mode. See Session modes.