From e922197126fe8174a64e9fa42e233c8d43ba6bc5 Mon Sep 17 00:00:00 2001 From: Zoltan Kochan Date: Tue, 5 May 2026 21:15:46 +0200 Subject: [PATCH] docs: add PR/issue/comment instructions for agents (#11475) Add a "Working with GitHub PRs, Issues, and Comments" section to AGENTS.md covering three rules: Keep PR title and description current when pushing new changes. Reply to resolved review comments with the resolution + commit hash and close the conversation. Sign all agent-authored comments, issues, and PRs with a footer that names the agent and model. --- AGENTS.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 07d866ed7f..2b79d862e4 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -189,6 +189,17 @@ try { } ``` +## Working with GitHub PRs, Issues, and Comments + +- **Keep PR titles and descriptions current.** When pushing new changes to a PR, review the title and description and update them if they no longer accurately reflect what the PR does. +- **Reply to and resolve review conversations.** Once a review comment has been addressed, reply to the thread with a description of the resolution including the commit hash that fixed it, then mark the conversation as resolved. +- **Sign all agent-authored content.** When posting a comment, creating an issue, or opening a PR, append a footer to the message indicating that it was written by an agent. The footer must include the name of the agent and the name of the model used. Example: + + ```markdown + --- + Written by an agent (Claude Code, claude-opus-4-7). + ``` + ## Resolving Conflicts in GitHub PRs Use `shell/resolve-pr-conflicts.sh` to resolve PR conflicts: