From 5bce222b0cc41cf518835b535dd48e28ff07fe31 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 31 May 2026 17:46:06 +0100 Subject: [PATCH] docs(agents): require related issue search --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 9245bf5558e6..30d48ae7c8c2 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -142,6 +142,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 work: search strong related issues/PRs before final; close proven dupes/fixed siblings. If none close, suggest one next related follow-up. - 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.