docs(agents): add PR review response guidance to AGENTS.md#2850
Merged
Conversation
…ding Adds a 'Responding to PR Review Comments' section to AGENTS.md so agents acting on PRs stop posting one reply per review comment. Directs them to post one summary comment per review round, disclose their identity and the human they're acting for, never click 'Resolve conversation', and re-request review once per round rather than after every push. Closes github#2849
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation guidance to reduce noisy agent behavior in PR review threads by standardizing how agents should respond to review feedback in this repository.
Changes:
- Adds a new “Responding to PR Review Comments” section to
AGENTS.md. - Provides concise directives encouraging a single top-level summary response per review round and limiting inline replies to cases where context is necessary.
Show a summary per file
| File | Description |
|---|---|
| AGENTS.md | Adds PR review response guidance to prevent agent comment flooding and improve review thread readability. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2849.
Summary
Adds a short "Responding to PR Review Comments" section to
AGENTS.md(between "Branch Naming Convention" and "Common Pitfalls") so agents acting on PRs in this repo stop posting one reply per review comment.Background
Recent PR review cycles have produced large numbers of agent-authored reply comments — one per reviewer finding, each starting with a "Fixed in
<sha>" status header that mirrors the reviewer's items 1:1. #2704 is the visible example: the latest Copilot review there generated 9 inline comments, and the author posted 9 near-identical replies in a row. That floods the conversation, buries the diff, and is visibly not how a human maintainer would respond.AGENTS.mdhad no guidance on this, so agents fell back to default per-comment-reply behavior.The new section
Six directive bullets, kept terse on purpose:
Out of scope
.github/copilot-instructions.mdor any agent-specific instruction file. If maintainers want this enforced on the Copilot coding-agent path specifically, that can be a follow-up.