From 832b6487e0ca8d755c28e0dd4367a5fcba5ff776 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 31 May 2026 15:36:35 +0100 Subject: [PATCH] docs: require live batch issue verification --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index a98d7af93df8..5296dc64f87c 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -143,6 +143,7 @@ Skills own workflows; root owns hard policy and routing. - 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. +- Before presenting a batch of issues/PRs, use smart subagents to verify live state and current `main`; omit closed/fixed items, and comment+close items already fixed on `main` when maintainer action is authorized. - 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.