Skip to content

Conversation

@plaskowski
Copy link

@plaskowski plaskowski commented Jul 21, 2025

Add a new tool that allows AI agents to reply to existing pull request comments. This tool uses GitHub's CreateCommentInReplyTo REST API to create threaded conversations on pull requests.

Features:

  • Reply to any existing PR comment using its ID
  • Proper error handling for missing parameters and API failures
  • Comprehensive test coverage (8 test cases)
  • Follows project patterns and conventions
  • Registered in pull_requests toolset as a write operation

Parameters:

  • owner: Repository owner (required)
  • repo: Repository name (required)
  • pullNumber: Pull request number (required)
  • commentId: ID of comment to reply to (required)
  • body: Reply text content (required)

This tool complements the existing add_comment_to_pending_review tool by enabling responses to already-posted comments, enhancing AI-powered code review workflows.

Closes: #635

Add a new tool that allows AI agents to reply to existing pull request comments.
This tool uses GitHub's CreateCommentInReplyTo REST API to create threaded
conversations on pull requests.

Features:
- Reply to any existing PR comment using its ID
- Proper error handling for missing parameters and API failures
- Comprehensive test coverage (8 test cases)
- Follows project patterns and conventions
- Registered in pull_requests toolset as a write operation

Parameters:
- owner: Repository owner (required)
- repo: Repository name (required)
- pullNumber: Pull request number (required)
- commentId: ID of comment to reply to (required)
- body: Reply text content (required)

This tool complements the existing add_comment_to_pending_review tool by
enabling responses to already-posted comments, enhancing AI-powered
code review workflows.

Closes: #N/A
@skanehira
Copy link

Hi @plaskowski
Thank you for creating this PR!

Is this PR ready for review?
I'd love to be able to use this feature soon.

@plaskowski
Copy link
Author

@skanehira I have been using it for a while from my fork. To be honest I don't plan to work on this soon so feel free to pick up the work to bring it to mergable state.

@ilyakamens
Copy link

@plaskowski is this what will enable Claude to reply to these kinds of comments?

If so, what needs to be done to bring this to a mergeable state? Happy to try to help.

@plaskowski
Copy link
Author

plaskowski commented Jan 7, 2026

@ilyakamens

is this what will enable Claude to reply to these kinds of comments?

yes

If so, what needs to be done to bring this to a mergeable state? Happy to try to help.

I will be honest - I have no idea as I have not yet read the contribution guideline. Most likely some test coverage and then maintainer review. The tool itself already works, I am using it (by using my fork built locally).

@ilyakamens
Copy link

@plaskowski, I've taken this up in another PR to get into a mergeable state. Can you describe how you've been using it locally so that I can do the same and test it myself?

@ilyakamens ilyakamens mentioned this pull request Jan 21, 2026
11 tasks
@plaskowski
Copy link
Author

plaskowski commented Jan 21, 2026 via email

@ilyakamens
Copy link

Oops, sorry. I was trying to ask how you ran it locally. Was it by following this and running it in Docker? https://github.com/github/github-mcp-server?tab=readme-ov-file#prerequisites-1

@plaskowski
Copy link
Author

plaskowski commented Jan 21, 2026 via email

@ilyakamens
Copy link

PR opened: #1856

We'll see how it goes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support replying to existing PR review comments

3 participants