From 17c8602a9cddd829d8e47aed7b002c8a77e5216d Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 31 May 2026 14:07:08 +0100 Subject: [PATCH] docs: require issue summaries in agent replies --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index fc87dad8dc3..93d8aedca3c 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -137,6 +137,7 @@ Skills own workflows; root owns hard policy and routing. - No unsolicited PR labels/retitles/rebases/fixups/landing. Comments/reviews ok only for reviewable findings, pre-merge proof, or close/duplicate reason after explicit close/sweep/landing request. - Maintainer decision closes the cluster: if deciding reported behavior/proposed fix is not planned, comment+close all directly associated open issues/PRs unless explicitly told to keep one open. Associated means linked PRs/issues, duplicates, companion workaround PRs, and the canonical issue for the rejected behavior. - Do not leave associated issues open for hypothetical future repros. Close with rationale; ask for a new issue or reopen only if concrete new evidence appears. Close comment states: decision, why, supported alternative, and what evidence would change the decision. +- Issue/PR numbers need a short summary every time; assume the reader has not opened or read them. - PR review answer: bug/behavior, URL(s), affected surface, provenance for regressions when traceable, best-fix judgment, evidence from code/tests/CI/current or shipped behavior. - PR reviewable findings: post them on the PR, not chat-only, so author sees actionable feedback. - Issue/PR final answer: last line is the full GitHub URL.