From ca4d0ef461c74669d24d1b2ad33224820132f177 Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Thu, 4 Jun 2026 08:41:23 -0500 Subject: [PATCH 1/3] docs(agents): add PR review response guidance to prevent comment flooding 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 #2849 --- AGENTS.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index ca3f2a537e..bf5cdf7e8b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -423,6 +423,17 @@ When an issue exists, include its number immediately after the prefix — this i --- +## Responding to PR Review Comments + +- If you are an agent working on behalf of a human, **disclose your identity in your PR comment** — name the agent (and model, if applicable) and the human you are acting for (e.g., "Posted on behalf of @user by GitHub Copilot (Claude Sonnet 4.5)"). +- Post **one** top-level summary comment per review round listing what changed and the commit SHA. Do not reply on every individual comment. +- Reply inline only when context is needed (disagreement, deferral, non-obvious fix). Keep it to a sentence or two. +- **Never click "Resolve conversation"** — that belongs to the reviewer or PR author. +- No emoji, no celebratory framing, no checklist mirroring the reviewer's items, no restating what the reviewer wrote. +- Re-request review once per round (when all feedback is addressed), not after every intermediate push. + +--- + ## Common Pitfalls 1. **Using shorthand keys for CLI-based integrations**: For CLI-based integrations (`requires_cli: True`), the `key` must match the executable name (e.g., `"cursor-agent"` not `"cursor"`). `shutil.which(key)` is used for CLI tool checks — mismatches require special-case mappings. IDE-based integrations (`requires_cli: False`) are not subject to this constraint. From 30aa49d81281d7359d3fe1b5c3d33570dbd3a610 Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Thu, 4 Jun 2026 08:44:01 -0500 Subject: [PATCH 2/3] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index bf5cdf7e8b..69abb6a8e3 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -425,7 +425,7 @@ When an issue exists, include its number immediately after the prefix — this i ## Responding to PR Review Comments -- If you are an agent working on behalf of a human, **disclose your identity in your PR comment** — name the agent (and model, if applicable) and the human you are acting for (e.g., "Posted on behalf of @user by GitHub Copilot (Claude Sonnet 4.5)"). +- If you are an agent working on behalf of a human, **disclose your identity in your PR comment** — name the agent (and model, if applicable) and the human you are acting for (e.g., "Posted on behalf of @user by GitHub Copilot (model: )"). - Post **one** top-level summary comment per review round listing what changed and the commit SHA. Do not reply on every individual comment. - Reply inline only when context is needed (disagreement, deferral, non-obvious fix). Keep it to a sentence or two. - **Never click "Resolve conversation"** — that belongs to the reviewer or PR author. From 9020ed36bd940b3d77d466e2c77397333037cc79 Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Thu, 4 Jun 2026 08:47:17 -0500 Subject: [PATCH 3/3] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 69abb6a8e3..4f0c9912a8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -425,7 +425,7 @@ When an issue exists, include its number immediately after the prefix — this i ## Responding to PR Review Comments -- If you are an agent working on behalf of a human, **disclose your identity in your PR comment** — name the agent (and model, if applicable) and the human you are acting for (e.g., "Posted on behalf of @user by GitHub Copilot (model: )"). +- If you are an agent working on behalf of a human, **disclose your identity in your PR comment** — name the agent (and model, if applicable) and the human you are acting for (e.g., "Posted on behalf of @user by GitHub Copilot (model: <name-if-known>)"). - Post **one** top-level summary comment per review round listing what changed and the commit SHA. Do not reply on every individual comment. - Reply inline only when context is needed (disagreement, deferral, non-obvious fix). Keep it to a sentence or two. - **Never click "Resolve conversation"** — that belongs to the reviewer or PR author.